A tool to perform simple linear regression between two variables
AI agents invoke linear_regression_calculator to trigger actions in JeffersonStats. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
The tool runs a statistical algorithm (linear regression) on input data and returns results. It does not read from or write to any persistent store, delete data, or move money. It falls under Execute because it performs a computation/calculation whose outputs depend on the arguments passed, similar to other analytical execution tools.
From the tool's definition 'perform simple linear regression between two variables' — executes a statistical computation on provided data
Attacks that exploit this kind of access
A tool to perform simple linear regression between two variables. It is categorised as a Execute tool in the JeffersonStats MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the JeffersonStats MCP server in PolicyLayer and add a rule for linear_regression_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.
linear_regression_calculator is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the linear_regression_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 linear_regression_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.
linear_regression_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 →