google_sheets_get_sheet_metadata
Get metadata for all sheets (tabs) in a spreadsheet, including sheet IDs, titles, row/column counts, and frozen rows/columns
This record as markdown: /tools/sagemcp-sagemcp/google-sheets-get-sheet-metadata.md
What google_sheets_get_sheet_metadata does on Sage MCP
AI agents call google_sheets_get_sheet_metadata 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_sheets_get_sheet_metadata is rated Low
This tool retrieves metadata about spreadsheet structure (sheet names, IDs, dimensions, freeze settings) without any side effects. It performs a read-only query operation on Google Sheets. The metadata retrieved is non-sensitive structural information that does not expose actual cell data, making the blast radius minimal even if misused by an agent.
From the tool's definition Tool name contains 'get' and description states 'Get metadata for all sheets...including sheet IDs, titles, row/column counts, and frozen rows/columns' — purely retrieves structural information without modifying data.
Attacks that exploit this kind of access
The rule that runs google_sheets_get_sheet_metadata 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_sheets_get_sheet_metadata, this is the rule to start with:
google_sheets_get_sheet_metadata 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_sheets_get_sheet_metadata call is checked against it from then on.
Questions about google_sheets_get_sheet_metadata
Get metadata for all sheets (tabs) in a spreadsheet, including sheet IDs, titles, row/column counts, and frozen rows/columns. 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_sheets_get_sheet_metadata: 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_sheets_get_sheet_metadata 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_sheets_get_sheet_metadata 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_sheets_get_sheet_metadata. 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_sheets_get_sheet_metadata 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