AI agents call get-doc to retrieve information from MCP-Google-Doc without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries a Google Doc without modifying it. The naming convention (get-*) and its position among write/destructive operations (create/update/delete) confirm it is a read-only retrieval operation. No side effects or data modification occurs. Low severity due to read-only nature and typical low sensitivity of document retrieval in isolation.
From the tool's definition Tool name 'get-doc' paired with sibling tools including 'create-doc', 'delete-doc', 'update-doc' indicates this retrieves document content.
Documented attack patterns abuse exactly the kind of access get-doc gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP-Google-Doc, and nothing reaches the server without passing your rules. This is the rule we recommend for get-doc:
{
"version": "1",
"default": "deny",
"tools": {
"get-doc": {}
}
}get-doc is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
get-doc. It is categorised as a Read tool in the MCP-Google-Doc MCP Server, which means it retrieves data without modifying state.
Register the MCP-Google-Doc MCP server in PolicyLayer and add a rule for get-doc: 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-Google-Doc. Nothing to install.
get-doc 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-doc 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-doc. 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-doc is provided by the MCP-Google-Doc MCP server (ophydami/mcp-google-doc). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 8 MCP-Google-Doc tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
8 MCP-Google-Doc tools catalogued and risk-classified — across an index of 42,500+ MCP servers.