gws_docs_read

Read the content of a Google Doc by document ID.

SERVERIconnect SOURCEiconnect-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/io-github-heznpc-iconnect/gws-docs-read.md

WHAT IT DOES

What gws_docs_read does on Iconnect

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

RISK

Why gws_docs_read is rated Low

This tool retrieves document content from Google Workspace by ID. It performs a query operation with no side effects—no data is created, modified, deleted, or executed. The action is purely informational. Severity is low because unauthorized reads of documents, while a confidentiality concern, have limited blast radius compared to write, execute, or destructive operations.

From the tool's definition Tool name 'gws_docs_read' and description 'Read the content of a Google Doc by document ID' explicitly indicate retrieval of data with no modification.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs gws_docs_read safely

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

gws_docs_read Allowed

gws_docs_read 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": {
    "gws_docs_read": {}
  }
}

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

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

FAQ

Questions about gws_docs_read

What does the gws_docs_read tool do? +

Read the content of a Google Doc by document ID. It is categorised as a Read tool in the Iconnect MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on gws_docs_read? +

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

What risk level is gws_docs_read? +

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

Can I rate-limit gws_docs_read? +

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

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

gws_docs_read is provided by the Iconnect MCP server (iconnect-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Iconnect, and thousands of servers like it.

This server

All 279 Iconnect 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 →