A tool to calculate the range (difference between max and min) of a collection
AI agents call range_calculator to retrieve information from JeffersonStats without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a statistical analysis tool that performs a read-only calculation on provided data. It computes a descriptive statistic (range = max - min) with no side effects, no data mutation, no code execution beyond arithmetic, and no destructive or financial operations. It fits squarely in the Read category with minimal risk if misused by an agent.
From the tool's definition Tool description states it 'calculate[s] the range (difference between max and min)' — a pure mathematical computation that retrieves and processes data without modification, deletion, execution of external commands, or financial impact.
Attacks that exploit this kind of access
A tool to calculate the range (difference between max and min) of a collection. It is categorised as a Read tool in the JeffersonStats MCP Server, which means it retrieves data without modifying state.
Register the JeffersonStats MCP server in PolicyLayer and add a rule for range_calculator: 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 JeffersonStats. Nothing to install.
range_calculator 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 range_calculator 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 range_calculator. 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.
range_calculator is provided by the JeffersonStats MCP server (sharabhshukla/jeffersonstatsmcp). 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 →