Get user data by ID.
AI agents call get_user_data to retrieve information from Demo MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves user data based on an ID parameter. The verb 'Get' and the absence of any language suggesting modification, deletion, or external execution (e.g., 'create', 'delete', 'execute', 'run') clearly indicate a read-only operation. The risk is low because retrieval alone does not cause irreversible changes, though actual severity depends on data sensitivity, which is not specified here.
From the tool's definition Tool name 'get_user_data' and description 'Get user data by ID' indicate a retrieval operation with no modification or deletion of data.
Attacks that exploit this kind of access
Get user data by ID. It is categorised as a Read tool in the Demo MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Demo MCP Server 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 Demo MCP Server. 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 Demo MCP Server MCP server (tdu-naifen/sample-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
get_user_data is one line of Demo MCP Server's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →