Search text across one sheet or all sheets and return matching cells.
AI agents call search_sheet to retrieve information from Google Workspace MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The search_sheet tool performs a read-only query operation across spreadsheet data. It retrieves and returns matching cells but does not create, modify, delete, or execute any operations. The blast radius of misuse is minimal—an attacker could discover sensitive information in sheets they have access to, but cannot alter data or trigger external actions. This is classified as Read with low severity.
From the tool's definition Tool description states 'Search text across one sheet or all sheets and return matching cells.' This is a search/query operation that retrieves data without modifying it.
Attacks that exploit this kind of access
Search text across one sheet or all sheets and return matching cells. It is categorised as a Read tool in the Google Workspace MCP MCP Server, which means it retrieves data without modifying state.
Register the Google Workspace MCP server in PolicyLayer and add a rule for search_sheet: 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 Workspace MCP. Nothing to install.
search_sheet 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 search_sheet 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 search_sheet. 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.
search_sheet is provided by the Google Workspace MCP server (ngoquocviet2001/google-workspace-mcp). 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 →