google_docs_search_documents
Search for Google Docs by title or content. Use owner_email to find docs owned by a specific person.
This record as markdown: /tools/sagemcp-sagemcp/google-docs-search-documents.md
What google_docs_search_documents does on Sage MCP
AI agents call google_docs_search_documents to retrieve information from Sage MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why google_docs_search_documents is rated Low
This tool performs document discovery and retrieval without modifying, executing code, deleting, or moving money. The blast radius of misuse is limited to unauthorized information disclosure of document metadata and possibly content, which while concerning in a multi-tenant environment, remains within the Read category.
From the tool's definition Tool name 'search_documents' and description 'Search for Google Docs by title or content' indicate retrieval and querying operations with no side effects. The capability to filter by 'owner_email' is still a read-only query parameter.
Attacks that exploit this kind of access
The rule that runs google_docs_search_documents safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Sage MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For google_docs_search_documents, this is the rule to start with:
google_docs_search_documents is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Sage MCP, apply this rule, and every google_docs_search_documents call is checked against it from then on.
Questions about google_docs_search_documents
Search for Google Docs by title or content. Use owner_email to find docs owned by a specific person. It is categorised as a Read tool in the Sage MCP MCP Server, which means it retrieves data without modifying state.
Register the Sage MCP server in PolicyLayer and add a rule for google_docs_search_documents: 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 Sage MCP. Nothing to install.
google_docs_search_documents 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 google_docs_search_documents 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 google_docs_search_documents. 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.
google_docs_search_documents is provided by the Sage MCP server (sagemcp/sagemcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Sage, and thousands of servers like it.
This server
Across the catalogue