AI agents call get-user-data to retrieve information from MCPX MCP Gateway 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 the current user. It performs a read-only query with no capability to modify, delete, or execute operations. The scope is limited to the authenticated user's own data, and the operation is reversible and non-destructive. While user data could be sensitive depending on context, the tool itself is fundamentally a read operation with minimal blast radius if misused by an AI agent.
From the tool's definition Tool name 'get-user-data' and description 'Returns the current user' indicate a query operation that retrieves user information without modification, deletion, or execution of side effects.
Documented attack patterns abuse exactly the kind of access get-user-data gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCPX MCP Gateway, and nothing reaches the server without passing your rules. This is the rule we recommend for get-user-data:
{
"version": "1",
"default": "deny",
"tools": {
"get-user-data": {}
}
}get-user-data is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Returns the current user. It is categorised as a Read tool in the MCPX MCP Gateway MCP Server, which means it retrieves data without modifying state.
Register the MCPX MCP Gateway 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 MCPX MCP Gateway. 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 MCPX MCP Gateway MCP server (thelunarcompany/lunar). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 14 MCPX MCP Gateway tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
14 MCPX MCP Gateway tools catalogued and risk-classified — across an index of 42,500+ MCP servers.