Get a single document by path
AI agents call get_document to retrieve information from Firebase Live MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only query of a single Firestore document. It retrieves data without any side effects, modifications, or irreversible actions. While it provides access to Firebase data, the severity is low because the blast radius of misuse is limited to unauthorized data disclosure rather than system-wide damage. Confidence is high given the explicit 'Get' verb and retrieval-only semantics.
From the tool's definition Tool name is 'get_document' and description states 'Get a single document by path' - purely a retrieval operation with no modification or deletion capability.
Attacks that exploit this kind of access
Get a single document by path. It is categorised as a Read tool in the Firebase Live MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Firebase Live MCP Server 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 Firebase Live MCP Server. 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 Firebase Live MCP Server MCP server (nigelthorne/firebase_live_mcp_server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →