get_document_content
AI agents call get_document_content to retrieve information from Mcp Google Sheets without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name 'get_document_content' indicates retrieval of spreadsheet data with no modification capability. The empty description reduces confidence slightly, but the context of a Google Sheets bridge server and the naming pattern (contrasted with write/destructive siblings like 'add_rows', 'batch_update', 'delete') strongly suggests this is a read-only data retrieval operation. No side effects expected.
From the tool's definition Tool name 'get_document_content' and server description 'reading, writing, and managing spreadsheet data' with emphasis on reading; sibling tools include 'get_multiple_sheet_data' which is clearly a read operation.
Attacks that exploit this kind of access
get_document_content. It is categorised as a Read tool in the Mcp Google Sheets MCP Server, which means it retrieves data without modifying state.
Register the Mcp Google Sheets MCP server in PolicyLayer and add a rule for get_document_content: 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 Sheets. Nothing to install.
get_document_content 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_document_content 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_document_content. 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_document_content is provided by the Mcp Google Sheets MCP server (yardobr/mcp-google-sheets). 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 →