get_document
Get a document from a Firestore database.
This record as markdown: /tools/com-googleapis-firestore-mcp/get-document.md
What get_document does on Mcp
AI agents call get_document to retrieve information from Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| 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 |
name | string | Yes | Required. The resource name of the Document to get. In the format: `projects/{project_id}/databases/{database_id}/documents/{document_path}`. |
readTime | string | — | Reads the version of the document at the given time. This must be a microsecond precision timestamp within the past one hour, or if Point-in-Time Recovery is en |
transaction | string | — | Reads the document in a transaction. |
requestOptions | object | — | Optional. The request options for this request. |
Parameters from the server's own tool schema.
Why get_document is rated Low
Even though get_document only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs get_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 get_document, this is the rule to start with:
get_document is read-only, so it stays allowed. 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 get_document call is checked against it from then on.
Questions about get_document
Get a document from a Firestore database. It is categorised as a Read tool in the Mcp MCP Server, which means it retrieves data without modifying state.
get_document accepts 5 parameters: mask, name, readTime, transaction, requestOptions. Required: name. 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 get_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.
get_document is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_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 get_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.
get_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