provision_postgres_project · Run402 MCP: Risk & Policy

WHAT IT DOES

What provision_postgres_project does on Run402

AI agents use provision_postgres_project to create or update resources in Run402 — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Run402 environment.

WHY IT NEEDS A POLICY

Why provision_postgres_project needs a policy

This tool creates a new Postgres database instance, which is a Write operation (provisioning/creating a resource). It may also trigger financial obligations via x402 payment, but the primary action is resource provisioning. The severity is high because misuse could spin up costly infrastructure, expose credentials, or incur charges at scale.

From the tool's definition 'Provision a new Postgres database' and 'Returns project credentials on success, or payment details if x402 payment is needed'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

provision_postgres_project Rate-limited

provision_postgres_project stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "provision_postgres_project": {
      "limits": [
        {
          "counter": "provision_postgres_project_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Run402, so you can run agents against it safely.

FAQ

Questions about provision_postgres_project

What does the provision_postgres_project tool do? +

Provision a new Postgres database. Returns project credentials on success, or payment details if x402 payment is needed. It is categorised as a Write tool in the Run402 MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on provision_postgres_project? +

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

What risk level is provision_postgres_project? +

provision_postgres_project is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit provision_postgres_project? +

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

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

provision_postgres_project is provided by the Run402 MCP server (kychee-com/run402). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.