A tool to test if a collection comes from a normal distribution
AI agents call normality_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.
This tool performs hypothesis testing on data to assess distributional properties. It retrieves statistical information about input data and returns test results without any side effects, reversible modifications, code execution, deletions, or financial implications. It is purely analytical and read-only in nature.
From the tool's definition Tool name 'normality_test' and description 'test if a collection comes from a normal distribution' indicate a statistical analysis function that queries/analyzes data without modifying, deleting, or executing external operations.
Attacks that exploit this kind of access
A tool to test if a collection comes from a normal distribution. 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 normality_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.
normality_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 normality_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 normality_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.
normality_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 →