performance_baseline

THE RISK

Low Risk

Why performance_baseline needs a policy

Establishing a performance baseline typically involves running queries to measure and record execution metrics (timing, resource usage). This is fundamentally a read/observe operation. It may write baseline records internally, but the primary action is measurement.

From the tool's definition 'Establish performance baselines for critical queries' — implies reading/measuring query performance metrics without modifying data

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

POLICY

How to control performance_baseline

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 performance_baseline:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "performance_baseline": {}
  }
}

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

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

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about performance_baseline

What does the performance_baseline tool do? +

Establish performance baselines for critical queries. 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 performance_baseline? +

Register the Postgres Mcp Legacy MCP server in PolicyLayer and add a rule for performance_baseline: 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 performance_baseline? +

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

Can I rate-limit performance_baseline? +

Yes. Add a rate_limit block to the performance_baseline 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 performance_baseline completely? +

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

performance_baseline 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.

CHECK YOUR STACK →