Cursor + xCloud

Secure sites and servers with Cursor on xCloud

Securing sites and servers with Cursor means asking the editor's agent to read your xCloud vulnerability findings and server protections while your plugin or theme code sits open beside it, and to change rules only after you confirm.

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

Set up Cursor All Cursor guides

YouWhich sites have open vulnerabilities? The booking plugin in this repo is ours.

vulnerabilities_indexread-only

Agentshop.example.com has one high finding in the booking plugin and two medium ones in a gallery plugin. The booking finding matches the escaping in includes/forms.php. I can suggest the edit here.

YouSuggest it. I will deploy, then rescan.

AgentOnce you deploy, tell me and I will start the rescan, then read the count again a minute later rather than assume it is clean.

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

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

1
Add xCloud to mcp.json with the compact URL
Cursor stops at 40 tools per server, and the full xCloud server advertises one tool per customer-facing operation, so start with the compact profile: five tools that still reach every operation. Put this in ~/.cursor/mcp.json for all projects, or .cursor/mcp.json inside one project.
JSON
```
{
  "mcpServers": {
    "xcloud": {
      "url": "https://app.xcloud.host/mcp?profile=compact"
    }
  }
}
```
2
Or add it from Cursor's MCP settings
Cursor's docs manage MCP servers from the Customize page. Add a new server there and paste the compact URL instead of editing the file. Use the plain https://app.xcloud.host/mcp URL only if your Cursor version loads every tool.
URL
```
https://app.xcloud.host/mcp?profile=compact
```
3
Sign in to xCloud
Cursor supports OAuth for remote servers and shows a login prompt next to xcloud. Click it, approve the teams and choose Read-only or Full access in the browser, then ask this to confirm.
Prompt
```
Who am I on xCloud?
```

Check it worked

Then ask Cursor for the job itself, for example:

Prompt

Which xCloud sites have open vulnerabilities? Rank them and show the top findings next to the plugin names.

In practice

How Does Security Work from Cursor?

In Cursor you are usually looking at code when the security question comes up. Maybe a scan flagged a plugin, and the plugin is one your team wrote. You open the agent panel and ask which sites have open vulnerabilities, and Cursor calls xCloud's team-wide rollup and answers with a ranked list. You did not switch to a dashboard, and the list sits next to the files it concerns. Because Cursor stops at 40 tools per server, the xCloud entry in mcp.json should use the compact profile. That keeps five tools in the picker while still reaching every security operation, so the vulnerability and firewall calls below all work from the same short list.

The editor context changes what a finding means. If the vulnerable component is your own theme or plugin and its source is in the workspace, Cursor can read the code that the finding points at, suggest the edit and leave you to review it as a normal diff. The part xCloud owns stays with xCloud: after you deploy, Cursor starts a rescan, which runs without a stop and finishes a little later, and then reads the count again before it tells you the finding has gone. If the fix is a third-party plugin, theme or core update, it stops for your approval and offers a backup first, as it does for every client.

Server work shows up the same way. Ask Cursor for the Frankfurt server perimeter and it reads the firewall rules, the Fail2Ban ban list and the SSH restriction status, then lays them out in the chat. When you ask it to ban an address or add a rule, it names the server and the effect before it acts, and it explains the lockout risk. It will not delete the default SSH rule. For dashboard-only protections such as the 8G firewall or the AI bot blocker, it tells you the path in the site's Tools section instead of claiming a change. Cursor's own tool approval is separate from xCloud's confirmation, so you may see both.

Cursor specific: Cursor stops at 40 tools per server, and the full xCloud server is far over that, so keep ?profile=compact in the URL for security work. A project-level .cursor/mcp.json travels with the repository, so if you use an API token instead of OAuth, keep it out of any file you commit, because a token that can change firewall rules is more sensitive than one that only reads findings.

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 Cursor 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 Cursor 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 Cursor 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 xCloud sites have open vulnerabilities? Rank them and show the top findings next to the plugin names.

Prompt

The finding on shop.example.com points at our own booking plugin. Read the code in this workspace, suggest the fix, then rescan after I deploy.

Prompt

List firewall rules and banned IPs on the Frankfurt server. Do not change anything yet.

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.

Cursor and Security: Frequently Asked Questions

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

Does the compact profile still reach the firewall and vulnerability tools in Cursor?

Yes. The compact profile keeps five tools in Cursor's picker and still reaches every customer-facing xCloud operation, including vulnerabilities, firewall rules and Fail2Ban. It exists so the server stays under Cursor's 40-tool cap.

Can Cursor fix the code behind a vulnerability finding?

If the finding points at your own plugin or theme and its source is in the workspace, Cursor can read it and suggest the edit for you to review. After you deploy, it can start a rescan through xCloud and check that the finding has gone.

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