AI agents call get-partial-view-siblings 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 information about partial views in the Umbraco CMS hierarchy. It performs a read-only operation to fetch data about sibling views based on a path parameter. There is no creation, modification, deletion, code execution, or financial impact. The blast radius of misuse is minimal—an attacker could only enumerate partial view structure, not alter content or execute code.
From the tool's definition Tool name 'get-partial-view-siblings' and description 'Gets sibling partial views for a given descendant path' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
Gets sibling partial views for a given descendant path. 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-partial-view-siblings: 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-partial-view-siblings 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-partial-view-siblings 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-partial-view-siblings. 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-partial-view-siblings 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 →