A tool to calculate the variance of a collection
AI agents call variance_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.
Variance calculation is a descriptive statistical operation that takes input data and produces a computed result. It does not create, modify, delete, or execute arbitrary code. The tool fits squarely within the Read category as it queries/analyzes data without side effects. All sibling tools (anova_calculator, chi_square_test, correlation_calculator, etc.) are similarly analytical.
From the tool's definition Tool description states 'A tool to calculate the variance of a collection' — a pure mathematical computation that retrieves/computes statistics from provided data with no side effects, state changes, or external operations.
Attacks that exploit this kind of access
A tool to calculate the variance 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 variance_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.
variance_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 variance_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 variance_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.
variance_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 →