pages.delete

Delete a hosted static website and its CDN resources. Removes the page from this Vee3 account after deleting upstream resources. Cost = 5 tokens.

SERVERVee3 SOURCEhttps://mcp.vee3.io/mcp

Critical RISK CLASS

Category Destructive

Parameters 11 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-vee3io-vee3/pages.delete.md

WHAT IT DOES

What pages.delete does on Vee3

AI agents call pages.delete to permanently remove resources in Vee3, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Parameter	Type	Required	Description
`page_id`	string	Yes	Page id to delete.

Parameters from the server's own tool schema.

RISK

Why pages.delete is rated Critical

Irreversibly deletes website and CDN resources; cannot be undone without recovery procedures.

From the tool's definition Delete a hosted static website and its CDN resources. Removes the page from this Vee3 account.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs pages.delete safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Vee3, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For pages.delete, this is the rule to start with:

pages.delete Hidden

pages.delete is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "pages.delete"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Vee3, apply this rule, and every pages.delete call is checked against it from then on.

FAQ

Questions about pages.delete

What does the pages.delete tool do? +

Delete a hosted static website and its CDN resources. Removes the page from this Vee3 account after deleting upstream resources. Cost = 5 tokens. It is categorised as a Destructive tool in the Vee3 MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

What parameters does pages.delete accept? +

pages.delete accepts 1 parameter: page_id. Required: page_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on pages.delete? +

Register the Vee3 MCP server in PolicyLayer and add a rule for pages.delete: 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 Vee3. Nothing to install.

What risk level is pages.delete? +

pages.delete 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 pages.delete? +

Yes. Add a rate_limit block to the pages.delete 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 pages.delete completely? +

Set action: deny in the PolicyLayer policy for pages.delete. 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 pages.delete? +

pages.delete is provided by the Vee3 MCP server (https://mcp.vee3.io/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Vee3, and thousands of servers like it.

This server

All 269 Vee3 tools → Critical-risk tools on this server →

Across the catalogue

All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Blast radius →Tool call approval →