Low Risk

stats_regression

Calculate linear regression analysis with coefficients and R-squared

How to control stats_regression ↓

What stats_regression does on Postgres Mcp Legacy

AI agents call stats_regression to retrieve information from Postgres Mcp Legacy without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why stats_regression needs a policy

This tool performs statistical computation (linear regression analysis) on existing data and returns analytical results like coefficients and R-squared values. It reads/queries data to produce calculations without modifying, deleting, or executing anything with side effects.

From the tool's definition Calculate linear regression analysis with coefficients and R-squared

Documented attack patterns abuse exactly the kind of access stats_regression gives an agent:

How to control stats_regression

PolicyLayer is an MCP gateway — it sits between your AI agents and Postgres Mcp Legacy, and nothing reaches the server without passing your rules. This is the rule we recommend for stats_regression:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "stats_regression": {}
  }
}

stats_regression is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Postgres Mcp Legacy — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about stats_regression

What does the stats_regression tool do? +

Calculate linear regression analysis with coefficients and R-squared. It is categorised as a Read tool in the Postgres Mcp Legacy MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on stats_regression? +

Register the Postgres Mcp Legacy MCP server in PolicyLayer and add a rule for stats_regression: 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 Postgres Mcp Legacy. Nothing to install.

What risk level is stats_regression? +

stats_regression is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit stats_regression? +

Yes. Add a rate_limit block to the stats_regression 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.

How do I block stats_regression completely? +

Set action: deny in the PolicyLayer policy for stats_regression. 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.

What MCP server provides stats_regression? +

stats_regression is provided by the Postgres Mcp Legacy MCP server (neverinfamous/postgres-mcp-legacy). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Postgres Mcp Legacy tool call.

Start from Postgres Mcp Legacy, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

60 Postgres Mcp Legacy tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.