Claude + xCloud

Secure sites and servers with Claude on xCloud

Securing sites and servers with Claude means asking Anthropic's chat assistant, on the web or in Claude Desktop, to report open vulnerabilities and server protections through the xCloud connector and to change a rule only after you agree.

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

Set up Claude All Claude guides

YouWhich of my sites have known plugin vulnerabilities? Worst first, please.

vulnerabilities_indexread-only

Agentshop.example.com has one critical finding in a form plugin and three high ones. blog.example.com has two medium findings. Nothing is open on your other nine sites.

YouIgnore the contact form finding on the blog. It is a false positive.

sites_vulnerabilities_ignoreneeds approval

AgentDone. I recorded your reason, that it is a false positive, and I can restore the finding any time you ask.

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

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

1
Add xCloud as a custom connector
In Claude, open Customize, then Connectors, and choose Add custom connector. Name it xcloud, paste this URL as the remote MCP server URL and finish the setup. Claude shows the xCloud sign-in page; choose the teams and Read-only or Full access.
URL
```
https://app.xcloud.host/mcp
```
2
Check the connection
Start a new chat, check that the xcloud connector is enabled for it, and ask this. Claude calls xCloud and names your account and the teams you approved.
Prompt
```
Who am I on xCloud?
```
3
On Team or Enterprise, add it as an owner
Members cannot add custom connectors on a Team plan. An Owner or Primary Owner adds it under Organization settings, then Connectors, with the same URL. On Enterprise, a custom role with Manage access to Libraries can add it too.
URL
```
https://app.xcloud.host/mcp
```

Check it worked

Then ask Claude for the job itself, for example:

Prompt

Which of my sites have known plugin vulnerabilities right now? Rank them worst first and tell me which one to deal with today.

In practice

How Does Security Work from Claude?

Most people who ask a security question in Claude are not in a terminal. You may run an agency, manage a handful of client sites or simply want a status you can read at your desk. You open a chat, make sure the xcloud connector is switched on for it and ask in ordinary sentences, for instance which of your sites have known plugin vulnerabilities. Claude calls xCloud's team-wide rollup, which covers every site you approved, and answers with a short ranked list instead of a wall of data. You can then ask a follow-up about one site and get the counts by severity and the findings behind them, with the plugin or theme named.

Because this is a conversation, it suits the part of security work that is mostly reading and deciding. You can ask Claude to explain a finding in plain words, tell you whether it looks like a false positive and draft a note for a client. If you decide to ignore a finding, you give the reason in the chat, Claude records it with the finding and tells you how to restore it later. A rescan runs without a stop and finishes a little later, so Claude checks again before it says anything is resolved. A plugin or theme update stops for your yes, and it offers a backup first.

On the server side, Claude reads firewall rules, Fail2Ban bans, the SSH restriction state and the sudo users, then summarises them without jargon. It names the server and the effect before it adds a rule, bans an address or unbans one. Some protections are not available from chat at all. The AI bot blocker, the 7G and 8G firewall and a single site's IP list are dashboard switches, so Claude points you to the site's Tools section and does not claim it changed them. Claude connects to xCloud from Anthropic's cloud, so the work does not depend on your own machine or network.

Claude specific: Claude shows what the connector returns, but the connector only has the access level you approved. A Read-only approval answers every question in this job and refuses the changes, so a rescan, an ignore or a firewall change fails until you reconnect with Full access. On a Team plan the connector belongs to the organization, so ask an Owner which level it was approved with before you rely on it for rule changes.

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

Which of my sites have known plugin vulnerabilities right now? Rank them worst first and tell me which one to deal with today.

Prompt

Run a vulnerability scan on shop.example.com. When it finishes, explain each finding in plain language and say which look like false positives.

Prompt

Show me the IPs Fail2Ban has banned on the Frankfurt server and whether SSH is limited to trusted addresses.

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 and Security: Frequently Asked Questions

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

Can Claude in chat ban an IP address on my xCloud server?

Yes, if the connector has Full access. Claude names the server and the effect, waits for your yes and then bans the address through Fail2Ban. It can also list the banned IPs and unban one on request.

Can I use Claude to switch on the AI bot blocker?

No. The AI bot blocker is a dashboard toggle under the site's Tools section, and Claude cannot flip it. It can tell you where the switch is and read what the site's logs show, but it will not say it changed a setting it cannot reach.

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