A tool to perform chi-square test of independence between two categorical variables
AI agents call chi_square_test 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.
Chi-square test is a statistical computation that analyzes relationships between variables but does not create, modify, delete, or execute arbitrary code. It reads input data and returns computed results with no side effects. This is characteristic of Read operations.
From the tool's definition Tool performs statistical analysis ('chi-square test of independence') on categorical variables. Description indicates computation/analysis only with no data modification, deletion, or external effects.
Attacks that exploit this kind of access
A tool to perform chi-square test of independence between two categorical variables. 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 chi_square_test: 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.
chi_square_test 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 chi_square_test 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 chi_square_test. 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.
chi_square_test 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 →