AI agents call get-document-blueprint-ancestors 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.
This tool queries and retrieves hierarchical information about a document blueprint in Umbraco CMS. It performs a read-only lookup operation that returns ancestor data without creating, modifying, deleting, or executing any actions. The low severity reflects minimal blast radius if misused by an agent - worst case would be unauthorized information disclosure of blueprint structure.
From the tool's definition Tool description states it 'Gets the ancestors of a document blueprint by Id' - this is a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
Gets the ancestors of a document blueprint by Id. 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 get-document-blueprint-ancestors: 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.
get-document-blueprint-ancestors 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 get-document-blueprint-ancestors 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 get-document-blueprint-ancestors. 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.
get-document-blueprint-ancestors 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 →