AI agents call get-user-data 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 user data without modifying, deleting, or executing any operations. It supports pagination and filtering, which are standard read capabilities. No side effects or irreversible actions are implied. The low severity reflects that data retrieval alone poses minimal risk unless the user data itself is highly sensitive, but the tool's function is purely informational.
From the tool's definition Tool name is 'get-user-data' and description states it 'Retrieves user data records with pagination and filtering'. The verb 'Retrieves' and the absence of any modification, deletion, or execution language indicate a read-only operation.
Attacks that exploit this kind of access
Retrieves user data records with pagination and filtering. 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-user-data: 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-user-data 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-user-data 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-user-data. 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-user-data 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 →