A tool to detect outliers in a collection using the IQR method
AI agents call outlier_detector 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 retrieves statistical insights from input data using a standard mathematical method (IQR). It has no side effects, does not modify data, does not execute arbitrary code, and does not trigger external operations. It is purely analytical, making it a Read category tool with low severity risk. The confidence is high because the description clearly indicates a computational analysis function.
From the tool's definition The tool 'outlier_detector' with description 'A tool to detect outliers in a collection using the IQR method' performs statistical analysis on provided data.
Attacks that exploit this kind of access
A tool to detect outliers in a collection using the IQR method. 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 outlier_detector: 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.
outlier_detector 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 outlier_detector 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 outlier_detector. 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.
outlier_detector 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 →