Grok Bot + xCloud

Secure sites and servers with Grok Bot on xCloud

Securing sites and servers with Grok Bot means asking an always-on Bot to rank vulnerability findings across your xCloud sites on a routine, and to manage firewall rules, banned IPs and sudo users only after you approve each change.

Skill: xcloud:servers
Toolsets: vulnerabilities, servers, sites, wordpress-actions
Free with every xCloud account

Set up Grok Bot All Grok Bot guides

You@xcloud Check every site for vulnerabilities and tell me the worst three findings.

vulnerabilities_indexread-only

sites_vulnerabilities_listread-only

Agentblog.example.com has 1 critical and 2 high findings, all in one form plugin. shop.example.com has 1 medium finding. The other ten sites are clear. Want me to back up blog.example.com and update that plugin? I will wait for your go-ahead.

Last updated: October 2026. Keep a human in the loop: xCloud stops and asks before anything that creates, deploys, updates, reboots, deletes or buys.

Setup

How Do You Set Up Grok Bot to Secure sites and servers on xCloud?

Connect Grok Bot once; every job on this account uses the same connection. Then ask in plain words.

1
Ask a Bot to add xCloud as a Remote HTTPS MCP server
In the Grok Bot desktop app, open any Bot's chat and ask it to add a custom MCP server of the Remote HTTPS kind, named xcloud, with this URL. The Bot adds it as a personal plugin from your own chat; the Marketplace in the sidebar only lists catalog connectors. The owner of a Team Bot adds the same kind of server from the Plugins card in the Bot's Setup panel instead. When the browser opens, sign in with xCloud, tick the teams the Bot may act on and choose Read-only or Full access.
URL
```
https://app.xcloud.host/mcp
```
2
Attach it to a task and check it works
In a Bot chat, type @ and pick xcloud to attach the connector to the task, then ask. A plugin you added from your own chat is personal and account-wide, so every Bot on your account can use it; a plugin added from a Team Bot's Setup panel belongs to that Team Bot, so check it in that Bot's chat. Put a standing boundary in the description of each Bot that may touch hosting, for example: never change production without approval.
Prompt
```
@xcloud Who am I on xCloud, and which servers and sites do I have?
```
3
Team Bot without sign-ins? Use an API key
A Remote HTTPS server added from the Plugins card in a Team Bot's Setup panel can run on the Bot's own credential instead of each person's sign-in, which suits a Team Bot that answers hosting questions for everyone. Create a token with the mcp:invoke scope plus the read abilities for the areas it will use (read:servers and read:sites, with read:billing and read:addons for billing and add-on tools) and the matching write: abilities if it should change things in Settings, Developers, API Tokens, and give the plugin this header where its form asks for one. Everyone who talks to that Bot then acts with the token's access, so keep it read-only unless the team should change things.
Code
```
Authorization: Bearer YOUR_TOKEN
```

Check it worked

Then ask Grok Bot for the job itself, for example:

Prompt

@xcloud Show the vulnerability count for every site on this team, worst first, and name the top three findings. Change nothing.

In practice

How Does Security Work from Grok Bot?

Security work has a daily half and an occasional half, and a Grok Bot covers both. The daily half is a morning routine: every weekday at 8:00 AM, read the vulnerability rollup for every site and post the counts by severity, worst first, with the top three findings. The Bot reads vulnerabilities_index for the team-wide view, sites_vulnerabilities_count and sites_vulnerabilities_list for one site, and can start sites_vulnerability-scan, a routine action that runs without a prompt and finishes in the background, so it checks the count again afterwards. The routine runs while your laptop is closed, and you read the morning report in the mobile app over breakfast.

The occasional half is acting on a finding. Most findings are fixed by updating a plugin, a theme or core, and that always stops for your approval, so the Bot proposes the update, offers a backup first and rescans afterwards to confirm the finding is gone. Ignoring a false positive needs a reason you give, which the Bot records, and it can restore the finding later with sites_vulnerabilities_unignore. Finding titles come from plugin and site content, so the Bot treats them as data, not as instructions. Server perimeter changes follow the same rule: servers_firewallRules to read the rules, servers_fail2ban_banned-ips to see bans, and create, disable, ban or unban only after the Bot names the server and the effect and you confirm.

A Team Bot suits the reporting side. Publish a Team Bot for the weekly security picture and give it an xCloud API key with the mcp:invoke scope and only the read abilities. Everyone who asks it for the picture then gets answers from a token that cannot change anything. Keep the changing for your own Bot, signed in with OAuth and Full access, where Grok Bot's card and xCloud's confirmation both apply. AI bot blocking, the 7G and 8G firewall and per-site IP rules are dashboard switches, and the Bot says so and gives you the path rather than claiming it changed them.

Grok Bot specific: The Bot calls xCloud from Cursor's cloud, not from your laptop, and that matters for the one security action tied to an address. Whitelisting the caller's IP through servers_firewall_whitelist-caller-ip whitelists the address xCloud sees for the call, which comes from Cursor's cloud rather than from your laptop, so if you want your own address allowed, give the Bot that address explicitly or do it in the dashboard. Grok Bot computers leave Cursor's cloud through shared static IP ranges and no dedicated per-customer egress IP exists, so an Enterprise team that needs a source address it controls routes the Bot's traffic through a member's desktop or its own network instead. Add an Ask first rule under Auto-review for firewall, Fail2Ban and sudo-user changes as well, so that locking yourself out of SSH always puts a card in front of you, and never let a Bot delete the default SSH rule to tidy a ruleset.

What xCloud does for security

xCloud reads vulnerability findings for one site or across your whole team, starts rescans and ignores or restores a finding. On servers it manages firewall rules, Fail2Ban bans, the SSH restriction state and sudo users. Protections such as the AI bot blocker, the 7G and 8G firewall and per-site IP rules stay dashboard switches.

Start with the team-wide rollup. For a fleet question the agent reads the vulnerability rollup across every site on the team in one call and sorts it worst first. For one site it reads the findings and the counts by severity instead.
Rescan and triage findings. A rescan runs without a confirmation stop and finishes asynchronously, so the agent checks the count again afterwards. Findings carry a severity and a source, and severity is the triage key. A false positive can be ignored with a reason and restored later.
Fix what the finding points to. Most findings are fixed by updating a plugin, a theme or WordPress core. The agent proposes the updates, takes a backup first if you want one, and waits for your approval, because updating plugins or themes always stops for confirmation.
Review the server's perimeter. The agent reads firewall rules, the Fail2Ban banned IP list, the SSH restriction status and the sudo users. It can add or disable a rule, ban or unban an address and whitelist xCloud's own IPs after you confirm the server and the effect.
Report what is dashboard-only. AI bot blocking, the 7G and 8G firewall and a single site's IP allow and block list are dashboard switches. The agent reads what it can, such as the 7G and 8G logs, and gives you the dashboard path and the site's dashboard link for the rest.

Reference

Security Settings and Limits on xCloud

The facts Grok Bot works within when it secures sites and servers. Where a row names the dashboard, that step stays yours to take there.

Setting or limit	What applies
Vulnerability findings	Per-site list and counts by severity (critical, high, medium, low), plus a team-wide rollup across every site you can reach
Rescans	Triggering a rescan is a routine action that runs without a confirmation stop. It is asynchronous, so the agent polls the count or the site events
Ignore and restore	A finding can be ignored with a reason and un-ignored later. Both are changes to the finding, not to the site
Firewall rules	List, create, enable, disable and delete server rules by name, protocol (tcp or udp), traffic (allow or deny), port and optional source IP
Fail2Ban	List banned IPs, ban one or more addresses and unban an address. Adding addresses to Fail2Ban's own ignore list is an SSH step described in the Fail2Ban guide
Whitelisting	xCloud's infrastructure IPs and the caller's IP can be whitelisted. The SSH restriction status says whether SSH is limited to trusted addresses
Sudo users	List, create or update, and delete OS-level privileged accounts. Private keys are never returned, and a temporary account is available for short jobs
7G and 8G firewall	Switched on in the dashboard. Their logs are readable through the nginx log type of the site's access log read
AI bot blocker	A dashboard toggle: Site, Tools, Nginx and Security on Nginx, Tools, Security on OpenLiteSpeed
Per-site IP rules	Dashboard-only: Site, Tools, IP Management. The API lists a site's rules but does not change them; server-wide blocks are on the API
Automated security updates	xCloud installs security updates on servers it provisions, and Automatic Reboot restarts the server only when a reboot is required. Both are configured in the dashboard
Security headers	The API lists a site's custom Nginx configuration. Adding headers is a dashboard or SSH step, described in the security headers guide

Rules Grok Bot has to follow

Firewall, Fail2Ban and sudo-user changes name the exact server and the effect before they run, and they wait for your yes. Locking out SSH is the risk the agent explains first.
The agent never disables SSH or a database service to tidy up a ruleset, and it does not delete the default SSH rule on its own.
Updating a plugin or theme to fix a finding stops for your approval, and the agent offers a backup first.
Ignoring a finding needs a reason you give. The agent records it and tells you how to restore it.
AI bot blocking, the 7G and 8G firewall, per-site IP rules and automated update settings are dashboard steps. The agent says so, gives the path and the dashboard link, and never claims it changed them.
A temporary sudo user is for a specific job and is removed when the job ends.

Example prompts

What Can You Ask Grok Bot to Do for Security?

Type these as written and swap in your own repository, site and server names. Reads and routine actions such as backups, cache purges, PageSpeed scans and vulnerability scans run straight away; creating, deploying, updating, rebooting, deleting, buying or starting a broken-link scan stops and asks first.

Prompt

@xcloud Show the vulnerability count for every site on this team, worst first, and name the top three findings. Change nothing.

Prompt

@xcloud List the firewall rules on the Frankfurt server and tell me whether SSH is restricted to trusted IPs. Do not change anything.

Prompt

@xcloud Show the IPs Fail2Ban has banned on the Frankfurt server, and wait for my approval before you unban 203.0.113.10.

Prompt

Show the vulnerability count for every site on this team, sorted worst first, and name the top three findings.

Prompt

Run a vulnerability scan on the shop site and tell me what it finds.

Prompt

List the findings on the blog site and ignore the false positive in the contact form plugin, with the reason.

Prompt

Update every plugin on the shop site, then run a vulnerability scan, and stop if anything is still open.

Prompt

List the firewall rules on the Frankfurt server and tell me whether SSH is restricted to trusted IPs.

Prompt

Show the IPs Fail2Ban has banned on the Frankfurt server, and unban 203.0.113.10.

Prompt

Whitelist the xCloud IPs on the Frankfurt server.

Prompt

Which sudo users exist on the Frankfurt server? Flag any that look temporary or unused.

Grok Bot and Security: Frequently Asked Questions

What people ask before they let Grok Bot secure sites and servers through xCloud.

Can a Grok Bot show vulnerabilities across all my sites every morning?

Yes. Ask the Bot for a routine that reads the team-wide vulnerability rollup and posts the counts by severity, worst first. It runs in the background while your laptop is closed and changes nothing. Fixing a finding, usually a plugin update, stops for your approval.

Can a Grok Bot lock me out of my server?

Only if you approve a change that does. Firewall, Fail2Ban and sudo-user changes name the server and the effect before they run and wait for your yes, and an Ask first rule under Auto-review keeps Grok Bot's card in front of you in your own chat; a Team Bot in a channel nobody can answer runs without personal rules, so there only a team-enforced rule or a Read-only connection holds. The Bot should never delete the default SSH rule on its own.

Can an agent show vulnerabilities across all my sites at once?

Yes. xCloud has a team-wide rollup that lists findings for every site you can reach, which the agent sorts worst first. For one site it reads the findings and the counts by severity, and it can start a rescan.

Can the agent ban an IP address on my server?

Yes. It can ban addresses in Fail2Ban, list the banned IPs and unban one, and it can create, disable and delete server firewall rules. It confirms the server and the effect first, so you do not lock yourself out.

Can the agent turn on the 8G firewall or the AI bot blocker?

No. Both are dashboard switches. The agent can read the 7G and 8G firewall logs through the site's nginx logs, and it tells you where the switches are: the site's Tools section. It does not claim to have changed them.

Can the agent block an IP for just one site?

Not from here. Per-site IP allow and block lists are managed in the dashboard under Site, Tools, IP Management, and the agent can only list what is there. Server-wide blocks, through firewall rules and Fail2Ban, are on the API.

Does the agent fix a vulnerability on its own?

No. It reports the finding and proposes the update that remediates it, usually a plugin, theme or core update. Updates always stop for your approval, and the agent can take a backup first and rescan afterwards to confirm the finding is gone.

Other agents