AI agents call jsr_get_user_scopes 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 existing data (user scope memberships) with no side effects, no code execution, no data modification, and no deletion. It is a straightforward read operation. Severity is low because the scope of exposure is limited to already-accessible membership information, and misuse would only leak data already known to the organization rather than create irreversible damage or execute arbitrary operations.
From the tool's definition Tool name contains 'get' and description states 'List scopes' — these are query operations that retrieve data without modification. The action is to retrieve information about a user's scope memberships.
Attacks that exploit this kind of access
List scopes that a specific user is a member of. 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_user_scopes: 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_user_scopes 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_user_scopes 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_user_scopes. 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_user_scopes 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 →