read_doc_structure

Read the full structure of a Google Doc including element indices, text formatting (bold, links, colors), table structure with cell indices, image/object IDs, header/footer IDs, document style (margins, page size), and named styles. Use this to understand document layout before making edits.

SERVERGoogle SOURCEztgluis/google-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/ztgluis-google-mcp/read-doc-structure.md

WHAT IT DOES

What read_doc_structure does on Google

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

RISK

Why read_doc_structure is rated Low

Even though read_doc_structure 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

RECOMMENDED RULE

The rule that runs read_doc_structure safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Google, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For read_doc_structure, this is the rule to start with:

read_doc_structure Allowed

read_doc_structure is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "read_doc_structure": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Google, apply this rule, and every read_doc_structure call is checked against it from then on.

FAQ

Questions about read_doc_structure

What does the read_doc_structure tool do? +

How do I enforce a policy on read_doc_structure? +

Register the Google MCP server in PolicyLayer and add a rule for read_doc_structure: 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_structure? +

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

Can I rate-limit read_doc_structure? +

Yes. Add a rate_limit block to the read_doc_structure 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_structure completely? +

Set action: deny in the PolicyLayer policy for read_doc_structure. 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_structure? +

read_doc_structure 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.

KEEP EXPLORING

More on Google, and thousands of servers like it.

This server

All 64 Google tools →

Across the catalogue

claude_read_file on Claude Bridge → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →