Read the content of a Google Document
AI agents call read_document to retrieve information from Google Workspace 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 operation on Google Docs. It retrieves and queries document content with no side effects, no data modification, and no external operations triggered. The only potential concern is if sensitive information is stored in documents, but the tool itself is fundamentally a data retrieval function. Classified as Read with low severity and high confidence.
From the tool's definition Tool name 'read_document' and description 'Read the content of a Google Document' explicitly indicate retrieval without modification.
Attacks that exploit this kind of access
Read the content of a Google Document. It is categorised as a Read tool in the Google Workspace MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Google Workspace MCP Server MCP server in PolicyLayer and add a rule for read_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 Google Workspace MCP Server. Nothing to install.
read_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 read_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 read_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.
read_document is provided by the Google Workspace MCP Server MCP server (pbulbule13/google-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 →