AI agents call jsr_list_scope_packages 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 and enumerates packages in a scope without modifying, creating, or deleting any data. It is a pure read operation with minimal blast radius if misused by an AI agent.
From the tool's definition Tool name contains 'list' and description states 'List all packages within a specific scope' — a query operation with no side effects.
Attacks that exploit this kind of access
List all packages within a specific scope. 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_list_scope_packages: 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_list_scope_packages 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_list_scope_packages 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_list_scope_packages. 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_list_scope_packages 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 →