calculate_route

THE RISK

Low Risk

Why calculate_route needs a policy

The tool name 'calculate_route' suggests a routing/navigation calculation which would typically be a read-like operation (computing a route without side effects). However, the description is completely empty, making it impossible to confirm. Given the context of a PostgreSQL MCP server (possibly with PostGIS), this could be a spatial query. With no description, confidence is very low.

From the tool's definition Tool name is 'calculate_route' and description is empty or uninformative.

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

POLICY

How to control calculate_route

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

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "calculate_route": {
      "limits": [
        {
          "counter": "calculate_route_rate",
          "window": "minute",
          "max": 60,
          "scope": "grant"
        }
      ]
    }
  }
}

calculate_route 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 calculate_route

What does the calculate_route tool do? +

calculate_route. 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 calculate_route? +

Register the AWS Labs postgres MCP Server MCP server in PolicyLayer and add a rule for calculate_route: 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 calculate_route? +

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

Can I rate-limit calculate_route? +

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

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

calculate_route 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 →