AI agents call jsr_get_stats 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 queries publicly available registry statistics. It has no side effects, does not create, modify, or delete data, and does not execute code or trigger external operations. It is a straightforward read-only operation returning informational data about the JSR registry.
From the tool's definition Tool name 'jsr_get_stats' and description 'Get registry statistics including newest packages, recent updates, and featured packages' indicate retrieval of aggregate statistical data with no modification, deletion, or execution of code.
Attacks that exploit this kind of access
Get registry statistics including newest packages, recent updates, and featured packages. 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_stats: 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_stats 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_stats 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_stats. 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_stats 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 →