Get descendant references for an element folder Use this to find all descendant references (child items) that are being referenced for a specific element folder. Useful for: • Impact analysis: Before deleting an element folder, see what content would be affected • Dependency tracking: Find all co...
AI agents call get-element-folder-referenced-descendants 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 retrieves and queries data about element folder hierarchies and their references without creating, modifying, deleting, or executing any operations. It is informational only, used to understand dependencies before potential actions. No side effects occur from calling this tool.
From the tool's definition Tool description explicitly states it 'Get[s] descendant references' and 'find[s] all descendant references (child items)' — purely retrieval operations with no modification, deletion, or execution.
Attacks that exploit this kind of access
Get descendant references for an element folder Use this to find all descendant references (child items) that are being referenced for a specific element folder. Useful for: • Impact analysis: Before deleting an element folder, see what content would be affected • Dependency tracking: Find all content using elements from a specific folder hierarchy • Content auditing: Identify which descendant element items are actually being used. 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-element-folder-referenced-descendants: 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-element-folder-referenced-descendants 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-element-folder-referenced-descendants 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-element-folder-referenced-descendants. 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-element-folder-referenced-descendants 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 →