Critical Risk →

nexus_delete_sitemap_page

Delete a page from a project

Part of the Nexus server.

nexus_delete_sitemap_page can permanently delete data in Nexus, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE NEXUS →

Free to start. No card required.

AI agents may call nexus_delete_sitemap_page to permanently remove or destroy resources in Nexus. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. PolicyLayer blocks destructive tools by default and requires explicit human approval before enabling them.

Without a policy, an AI agent could call nexus_delete_sitemap_page in a loop, permanently destroying resources in Nexus. There is no undo for destructive operations. PolicyLayer blocks this tool by default and only allows it when a human explicitly approves the action.

Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "nexus_delete_sitemap_page"
  ]
}

See the full Nexus policy for all 41 tools.

Get this rule live on your own Nexus server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY NEXUS →

View all 41 tools →

These attack patterns abuse exactly the kind of access nexus_delete_sitemap_page gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so nexus_delete_sitemap_page only ever does what you allow.

SECURE NEXUS →

Other destructive tools across the catalogue. The same approach applies to each: deny by default, or require human approval.

What does the nexus_delete_sitemap_page tool do? +

Delete a page from a project. It is categorised as a Destructive tool in the Nexus MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on nexus_delete_sitemap_page? +

Register the Nexus MCP server in PolicyLayer and add a rule for nexus_delete_sitemap_page: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Nexus. Nothing to install.

What risk level is nexus_delete_sitemap_page? +

nexus_delete_sitemap_page is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit nexus_delete_sitemap_page? +

Yes. Add a rate_limit block to the nexus_delete_sitemap_page rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.

How do I block nexus_delete_sitemap_page completely? +

Set action: deny in the PolicyLayer policy for nexus_delete_sitemap_page. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.

What MCP server provides nexus_delete_sitemap_page? +

nexus_delete_sitemap_page is provided by the Nexus MCP server (nexus-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Nexus tool call.

Deterministic rules across all 41 Nexus tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.