sp-performance

THE RISK

Low Risk

Why sp-performance needs a policy

The tool name 'sp-performance' could relate to stored procedure performance analysis (a Read operation) in the context of a PostgreSQL MCP server, but the description is completely empty. Without further information, it is not possible to confidently assign a more specific category. The name suggests a read/diagnostic operation, but this is speculative.

From the tool's definition Tool name is 'sp-performance' and description is empty or uninformative.

Documented attack patterns abuse exactly the kind of access sp-performance gives an agent:

POLICY

How to control sp-performance

PolicyLayer is an MCP gateway — it sits between your AI agents and AWS Labs postgres MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for sp-performance:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "sp-performance": {
      "limits": [
        {
          "counter": "sp-performance_rate",
          "window": "minute",
          "max": 60,
          "scope": "grant"
        }
      ]
    }
  }
}

sp-performance gets a rate cap, and everything else on the server is denied unless you say otherwise.

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

SET A RULE FOR THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

Other tools on other servers

Android Forensics ADB MCP Server generate_app_analysis_report Ethereum Tools add Math MCP Server complex_analysis_suite Crypto_MCP aes_encrypt

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Tool risk categories → How PolicyLayer classifies MCP tools by what they can do.
MCP tool → What an MCP tool is and how clients discover and call it.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about sp-performance

What does the sp-performance tool do? +

sp-performance. It is categorised as a Other tool in the AWS Labs postgres MCP Server MCP Server, which means it performs auxiliary operations.

How do I enforce a policy on sp-performance? +

Register the AWS Labs postgres MCP Server MCP server in PolicyLayer and add a rule for sp-performance: 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 AWS Labs postgres MCP Server. Nothing to install.

What risk level is sp-performance? +

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

Can I rate-limit sp-performance? +

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

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

sp-performance is provided by the AWS Labs postgres MCP Server MCP server (awslabs.postgres-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every AWS Labs postgres MCP Server tool call.

Start from AWS Labs postgres MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →