Critical Risk →

page.claim

Claim an anonymous demo page into the authenticated account using the pageId and editToken returned by page.create. Use this only when the user wants to keep or manage the website permanently.

Part of the Create Web Page server.

page.claim can permanently delete data in Create Web Page, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE CREATE WEB PAGE →

Free to start. No card required.

AI agents may call page.claim to permanently remove or destroy resources in Create Web Page. 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 page.claim in a loop, permanently destroying resources in Create Web Page. 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": [
    "page.claim"
  ]
}

See the full Create Web Page policy for all 23 tools.

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

ENFORCE ON MY CREATE WEB PAGE →

View all 23 tools →

These attack patterns abuse exactly the kind of access page.claim 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 page.claim only ever does what you allow.

SECURE CREATE WEB PAGE →

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

What does the page.claim tool do? +

Claim an anonymous demo page into the authenticated account using the pageId and editToken returned by page.create. Use this only when the user wants to keep or manage the website permanently.. It is categorised as a Destructive tool in the Create Web Page 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 page.claim? +

Register the Create Web Page MCP server in PolicyLayer and add a rule for page.claim: 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 Create Web Page. Nothing to install.

What risk level is page.claim? +

page.claim 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 page.claim? +

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

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

page.claim is provided by the Create Web Page MCP server (https://create-web-page.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Create Web Page tool call.

Deterministic rules across all 23 Create Web Page 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.