AI agents call jsr_get_current_user to retrieve information from JSR MCP 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 currently authenticated user. It performs a query operation that returns data without creating, modifying, deleting, or executing any actions. There are no side effects, making it a Read operation. Severity is low because user profile information is typically non-sensitive and the operation poses minimal risk if misused by an AI agent.
From the tool's definition Tool name 'jsr_get_current_user' and description 'Get details of the authenticated user' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
Get details of the authenticated user. It is categorised as a Read tool in the JSR MCP MCP Server, which means it retrieves data without modifying state.
Register the JSR MCP server in PolicyLayer and add a rule for jsr_get_current_user: 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 JSR MCP. Nothing to install.
jsr_get_current_user 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 jsr_get_current_user 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 jsr_get_current_user. 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.
jsr_get_current_user is provided by the JSR MCP server (wyattjoh/jsr-mcp). 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 →