AI agents call get-member-by-id-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 information about references without creating, modifying, deleting, or executing any operations. It is a pure read operation that queries member descendant references in the Umbraco CMS, presenting no risk of data modification or destructive action.
From the tool's definition Tool name includes 'get-' prefix and description states 'Get descendant references' — retrieves data about descendant references for a member without modification. The action is a query/lookup operation with no side effects.
Attacks that exploit this kind of access
Get descendant references for a member Use this to find all descendant references that are being referenced for a specific member account. 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-member-by-id-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-member-by-id-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-member-by-id-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-member-by-id-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-member-by-id-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 →