datastore_insert · MCP Datastore Server MCP: Risk & Policy

WHAT IT DOES

What datastore_insert does on MCP Datastore Server

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

WHY IT NEEDS A POLICY

Why datastore_insert needs a policy

The tool creates new records in Google Firestore Datastore, which is a reversible Write operation. While it modifies state, insertions can be undone via deletion. Severity is medium because unauthorized inserts could corrupt data integrity or populate the database with malicious content, but the impact depends on what data is inserted and the application's reliance on data consistency.

From the tool's definition Tool name is 'datastore_insert' and description states 'Insert a new entity into Datastore'. This creates new data in a persistent database.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

datastore_insert Rate-limited

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

FAQ

Questions about datastore_insert

What does the datastore_insert tool do? +

Insert a new entity into Datastore. It is categorised as a Write tool in the MCP Datastore Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on datastore_insert? +

Register the MCP Datastore Server MCP server in PolicyLayer and add a rule for datastore_insert: 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_insert? +

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

Can I rate-limit datastore_insert? +

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

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

datastore_insert 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.