Low Risk

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

How to control google_sheets_get_sheet_metadata ↓

AI agents call google_sheets_get_sheet_metadata to retrieve information from Sage MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

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.

Documented attack patterns abuse exactly the kind of access google_sheets_get_sheet_metadata gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Sage MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for google_sheets_get_sheet_metadata:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "google_sheets_get_sheet_metadata": {}
  }
}

google_sheets_get_sheet_metadata is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Sage MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the google_sheets_get_sheet_metadata tool do? +

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.

How do I enforce a policy on google_sheets_get_sheet_metadata? +

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.

What risk level is google_sheets_get_sheet_metadata? +

google_sheets_get_sheet_metadata is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit google_sheets_get_sheet_metadata? +

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.

How do I block google_sheets_get_sheet_metadata completely? +

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.

What MCP server provides google_sheets_get_sheet_metadata? +

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.

Enforce policy on every Sage MCP tool call.

Deterministic rules across all 359 Sage MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

359 Sage MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.