claim_site
Make a previously-anonymous site permanent under the authenticated account (requires auth + the claimToken from publish_site).
This record as markdown: /tools/ai-dataecho-mcp/claim-site.md
What claim_site does on Mcp
AI agents use claim_site to create or update resources in Mcp, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
slug | string | Yes | Site slug |
claimToken | string | Yes | Claim token returned by the anonymous publish |
Parameters from the server's own tool schema.
Why claim_site is rated Medium
This is classified as Write rather than Execute because the tool modifies data (site ownership/account association) reversibly—the claim could theoretically be undone or transferred. It does not execute arbitrary code or shell commands, nor does it destructively delete data.
From the tool's definition The tool 'claim_site' performs a state-changing operation: it converts a previously-anonymous site into a permanent, authenticated account association.
Attacks that exploit this kind of access
The rule that runs claim_site safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For claim_site, this is the rule to start with:
claim_site stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp, apply this rule, and every claim_site call is checked against it from then on.
Questions about claim_site
Make a previously-anonymous site permanent under the authenticated account (requires auth + the claimToken from publish_site). It is categorised as a Write tool in the Mcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
claim_site accepts 2 parameters: slug, claimToken. Required: slug, claimToken. The full parameter table on this page comes from the server's own tool schema.
Register the MCP server in PolicyLayer and add a rule for claim_site: 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 Mcp. Nothing to install.
claim_site is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the claim_site 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.
Set action: deny in the PolicyLayer policy for claim_site. 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.
claim_site is provided by the MCP server (https://dataecho.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on , and thousands of servers like it.
This server
Across the catalogue