List all sheets in the Google Spreadsheet
AI agents call list_sheets to retrieve information from Google Sheets MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only retrieves/enumerates existing sheets without creating, modifying, or deleting any data. It is a non-destructive read operation with minimal blast radius if misused by an agent — worst case it exposes the names of sheets in a spreadsheet, which is low-sensitivity metadata. Confidence is high because the name and description clearly indicate a listing/query function.
From the tool's definition Tool name is 'list_sheets' and description states 'List all sheets in the Google Spreadsheet' — a query operation that retrieves metadata about available sheets with no modification or side effects.
Attacks that exploit this kind of access
List all sheets in the Google Spreadsheet. It is categorised as a Read tool in the Google Sheets MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Google Sheets MCP Server MCP server in PolicyLayer and add a rule for list_sheets: 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 Sheets MCP Server. Nothing to install.
list_sheets 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 list_sheets 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 list_sheets. 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.
list_sheets is provided by the Google Sheets MCP Server MCP server (matty-v/google-sheets-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 →