read_doc

Read a Google Doc as plain text / markdown

Server Google ztgluis/google-mcp
Category Read
Risk class Low
Parameters 00 required

What read_doc does on Google

AI agents call read_doc to retrieve information from Google without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why read_doc needs a policy

This tool retrieves and queries document data with no side effects. Reading a document is a passive operation that does not create, modify, delete, or execute any actions. It poses minimal risk as it only exposes document content already accessible to the authenticated user.

From the tool's definition Tool name 'read_doc' and description 'Read a Google Doc as plain text / markdown' explicitly indicate retrieval of document content without modification.

Questions about read_doc

What does the read_doc tool do? +

Read a Google Doc as plain text / markdown. It is categorised as a Read tool in the Google MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on read_doc? +

Register the Google MCP server in PolicyLayer and add a rule for read_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 Google. Nothing to install.

What risk level is read_doc? +

read_doc is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit read_doc? +

Yes. Add a rate_limit block to the read_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.

How do I block read_doc completely? +

Set action: deny in the PolicyLayer policy for read_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.

What MCP server provides read_doc? +

read_doc is provided by the Google MCP server (ztgluis/google-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.