datastore_runInTransaction · MCP Datastore Server MCP

WHAT IT DOES

What datastore_runInTransaction does on MCP Datastore Server

AI agents invoke datastore_runInTransaction to trigger actions in MCP Datastore Server. 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 datastore_runInTransaction needs a policy

This tool executes multiple Firestore operations within a transaction boundary. While transactions themselves provide consistency guarantees, the tool's purpose is to trigger execution of whatever operations are specified within the transaction.

From the tool's definition Tool name 'datastore_runInTransaction' combined with description 'Execute multiple operations within a transaction' indicates execution of arbitrary database operations.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

datastore_runInTransaction Rate-limited

datastore_runInTransaction 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": {
    "datastore_runInTransaction": {
      "limits": [
        {
          "counter": "datastore_runintransaction_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 MCP Datastore Server, so you can run agents against it safely.

FAQ

Questions about datastore_runInTransaction

What does the datastore_runInTransaction tool do? +

Execute multiple operations within a transaction. It is categorised as a Execute tool in the MCP Datastore Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on datastore_runInTransaction? +

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

What risk level is datastore_runInTransaction? +

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

Can I rate-limit datastore_runInTransaction? +

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

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

datastore_runInTransaction is provided by the MCP Datastore Server MCP server (petekmet/mcp-gcp-datastore). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.