update_document
Update a document from a Firestore database.
This record as markdown: /tools/com-googleapis-firestore-mcp/update-document.md
What update_document does on Mcp
AI agents use update_document to create or update resources in Mcp, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
mask | object | — | The fields to return. If not set, returns all fields. If the document has a field that is not present in this mask, that field will not be returned in the respo |
document | object | Yes | Required. The updated document. Creates the document if it does not already exist. |
updateMask | object | — | The fields to update. None of the field paths in the mask may contain a reserved name. If the document exists on the server and has fields not referenced in the |
requestOptions | object | — | Optional. The request options for this request. |
currentDocument | object | — | An optional precondition on the document. The request will fail if this is set and not met by the target document. |
Parameters from the server's own tool schema.
Why update_document is rated Medium
An AI agent can call update_document faster than any human can review: one bad instruction and it creates or modifies resources in Mcp by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs update_document safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For update_document, this is the rule to start with:
update_document 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp, apply this rule, and every update_document call is checked against it from then on.
Questions about update_document
Update a document from a Firestore database. It is categorised as a Write tool in the Mcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
update_document accepts 5 parameters: mask, document, updateMask, requestOptions, currentDocument. Required: document. The full parameter table on this page comes from the server's own tool schema.
Register the MCP server in PolicyLayer and add a rule for update_document: 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. Nothing to install.
update_document is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the update_document 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.
Set action: deny in the PolicyLayer policy for update_document. 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.
update_document is provided by the MCP server (https://firestore.googleapis.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on , and thousands of servers like it.
This server
Across the catalogue