datastore_allocateIds · MCP Datastore Server MCP

WHAT IT DOES

What datastore_allocateIds does on MCP Datastore Server

AI agents use datastore_allocateIds 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_allocateIds needs a policy

ID allocation modifies the state of the Datastore by assigning identifiers to incomplete keys, which is a write-class operation. It is reversible (allocated IDs can be abandoned without use) and has minimal blast radius compared to other write operations.

From the tool's definition Tool name 'datastore_allocateIds' and description 'Allocate IDs for incomplete keys' indicate the tool creates or assigns identifiers in Firestore/Datastore.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

datastore_allocateIds Rate-limited

datastore_allocateIds 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_allocateIds": {
      "limits": [
        {
          "counter": "datastore_allocateids_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_allocateIds

What does the datastore_allocateIds tool do? +

Allocate IDs for incomplete keys. 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_allocateIds? +

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

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

Can I rate-limit datastore_allocateIds? +

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

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

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