AI agents call get-member-are-referenced 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 or checks information about whether member accounts are referenced in content—a read-only operation with no side effects, data modification, or destructive capability. It is a simple verification/query action typical of Read category tools.
From the tool's definition Tool name 'get-member-are-referenced' and description 'Check if member accounts are referenced' and 'Use this to verify if specific member accounts are being referenced by content' indicate a query/lookup operation with no modification or deletion.
Attacks that exploit this kind of access
Check if member accounts are referenced Use this to verify if specific member accounts are being referenced by content. 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-are-referenced: 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-are-referenced 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-are-referenced 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-are-referenced. 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-are-referenced 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 →