AI agents call validate-document-type-post to retrieve information from Mcp Dev without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Although the tool uses HTTP POST (which typically modifies data), the description explicitly states it does not persist changes. This makes it a validation/checking operation equivalent to a read operation. The tool retrieves validation results without creating, modifying, deleting, or executing any irreversible actions.
From the tool's definition Tool description states 'Validates a document type using the Umbraco API (POST, does not persist changes).' The explicit clarification that it 'does not persist changes' indicates this is a read-only validation operation with no side effects.
Attacks that exploit this kind of access
Validates a document type using the Umbraco API (POST, does not persist changes). It is categorised as a Read tool in the Mcp Dev MCP Server, which means it retrieves data without modifying state.
Register the Mcp Dev MCP server in PolicyLayer and add a rule for validate-document-type-post: 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 Dev. Nothing to install.
validate-document-type-post is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the validate-document-type-post 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 validate-document-type-post. 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.
validate-document-type-post is provided by the Mcp Dev MCP server (@umbraco-cms/mcp-dev). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →