execute_mutation · Instant Db MCP: Risk & Policy

WHAT IT DOES

What execute_mutation does on Instant Db

AI agents invoke execute_mutation to trigger actions in Instant Db. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why execute_mutation needs a policy

This tool executes arbitrary DML statements (INSERT, UPDATE, DELETE) against a database. While it rejects DDL and SELECT, it can still modify or delete data at scale through arbitrary UPDATE/DELETE statements. DELETE operations make this potentially destructive, but since it runs inside a transaction (implying rollback capability), it sits at Execute/Destructive boundary.

From the tool's definition Execute a DML statement (INSERT/UPDATE/DELETE) against a database... Runs inside a transaction.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

execute_mutation Rate-limited

execute_mutation stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "execute_mutation": {
      "limits": [
        {
          "counter": "execute_mutation_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about execute_mutation

What does the execute_mutation tool do? +

Execute a DML statement (INSERT/UPDATE/DELETE) against a database. DDL and SELECT are rejected. Runs inside a transaction. It is categorised as a Execute tool in the Instant Db MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on execute_mutation? +

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

What risk level is execute_mutation? +

execute_mutation is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit execute_mutation? +

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

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

execute_mutation is provided by the Instant Db MCP server (urbushey/mcp-db). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.