Claude Code + xCloud

Secure sites and servers with Claude Code on xCloud

Securing sites and servers with Claude Code means asking Anthropic's terminal agent to read vulnerability findings across your team, review each server's perimeter and make a firewall or ban change only after you confirm it, all through xCloud.

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

Set up Claude Code All Claude Code guides

YouWhich of my sites are most exposed? Worst first.

vulnerabilities_indexread-only

Agentshop.example.com has 1 critical and 3 high, all in two plugins. blog.example.com has 2 medium. The other nine sites show nothing open. Want the findings on the shop?

YouYes, and check the Frankfurt server perimeter too.

servers_firewallRulesread-only

AgentFrankfurt allows SSH, HTTP and HTTPS only. Fail2Ban has banned 14 addresses. I can ban another address or rescan the shop, but I will name the server and the effect before either.

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 Claude Code to Secure sites and servers on xCloud?

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

1
Add the xCloud MCP server
Run this in your terminal, then type /mcp inside Claude Code, pick xcloud and choose Authenticate. The browser opens on the xCloud approval screen, where you tick the teams and choose Read-only or Full access.
Terminal
```
claude mcp add xcloud --transport http https://app.xcloud.host/mcp
```
2
Install the xCloud skills plugin
Optional but recommended. Inside Claude Code, add the xCloud marketplace, install the plugin and reload. The nine skills teach Claude Code which tool to reach for, how to dry-run and confirm, how to poll a long job and how to diagnose a failed deploy.
Terminal
```
/plugin marketplace add xCloudDev/xcloud-agent-skills
/plugin install xcloud@xcloud-agent-skills
/reload-plugins
```
3
No browser? Use an API key
For a headless or CI machine, 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 pass it as a header. Keep the single quotes: xCloud tokens contain a pipe character.
Terminal
```
claude mcp add xcloud --transport http https://app.xcloud.host/mcp \
  --header 'Authorization: Bearer YOUR_TOKEN'
```

Check it worked

Then ask Claude Code for the job itself, for example:

Prompt

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

In practice

How Does Security Work from Claude Code?

A security question rarely arrives as one tidy task. You are in a terminal, you wonder which of your sites are exposed, and you would like an answer sorted worst first. Claude Code handles that opening move well. You type the question, it calls vulnerabilities_index for the whole team in one read, and it prints a short ranking with the site, the severity and the title of the top findings. You did not name a site, and you did not leave the session you were already in. When one site stands out, Claude Code switches to sites_vulnerabilities_count for the counts by severity and sites_vulnerabilities_list for the findings themselves.

From there the session behaves like a careful colleague. A rescan runs without a stop, because it is a routine action, but it finishes in the background, so Claude Code checks the count again a little later rather than telling you it is clean on the strength of the first response. Most findings are fixed by updating a plugin, a theme or core, and that is the point where Claude Code stops and asks. It offers a backup first, then waits for your approval before it touches anything. Server work follows the same rhythm. It reads servers_firewallRules, servers_fail2ban_banned-ips and servers_firewall_ssh-restriction-status together, summarises what is open and what is banned, and says plainly if SSH is not restricted to trusted addresses.

The extra thing Claude Code brings is the working directory. If the repository you are in is a WordPress theme or a custom plugin, it can read the code behind a finding, propose the edit and leave the commit to you, while xCloud does the rescan after you deploy. When you ask it to ban an address or add a rule, it names the exact server and the effect before it sends anything, and it explains the lockout risk first. It will not delete the default SSH rule to tidy a ruleset. Where a protection is a dashboard switch, such as the AI bot blocker or the 8G firewall, it says so and gives you the path instead of pretending it changed it.

Claude Code specific: Claude Code can only change a rule or a ban if the connection was approved with Full access. If you chose Read-only on the approval screen, the reads work and the changes come back refused, so type /mcp, pick xcloud, authenticate again and approve Full access for the teams you mean. Treat the refusal as a safe default, not a fault, and choose the level on purpose for each machine you use.

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 Claude Code 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 Claude Code 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 Claude Code 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

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

Prompt

Rescan shop.example.com, wait for it to finish and tell me whether the critical finding is still open.

Prompt

List firewall rules and Fail2Ban bans on the Frankfurt server. Is SSH restricted to trusted IPs?

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.

Claude Code and Security: Frequently Asked Questions

What people ask before they let Claude Code secure sites and servers through xCloud.

Can Claude Code fix a vulnerability that xCloud reports?

It can propose the fix and, with your approval, run it. Most findings are cleared by a plugin, theme or core update, which always stops for your confirmation. Claude Code can take a backup first and rescan afterwards to confirm the finding is gone.

Will Claude Code lock me out of SSH when it edits firewall rules?

It is built to avoid that. Claude Code names the server and the effect before it creates, disables or deletes a rule, and it does not remove the default SSH rule on its own. You still decide, so read the rule it describes before you say yes.

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