GOOGLESUPER_EXECUTE_SQL
Execute SQL queries against Google Sheets tables. Supports SELECT, INSERT, UPDATE, and DELETE operations with familiar SQL syntax. Tables are automatically detected and mapped from the spreadsheet structure.
This record as markdown: /tools/googlesuper/googlesuper-execute-sql.md
What GOOGLESUPER_EXECUTE_SQL does on Google Super
AI agents invoke GOOGLESUPER_EXECUTE_SQL to trigger actions in Google Super. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
sql | string | — | SQL query to execute. Supports SELECT, INSERT, UPDATE, DELETE operations. |
dry_run | boolean | — | Preview changes without applying them (for write operations) |
delete_method | string | — | For DELETE operations: 'clear' preserves row structure, 'remove_rows' shifts data up |
spreadsheet_id | string | — | Google Sheets ID |
Parameters from the server's own tool schema.
Why GOOGLESUPER_EXECUTE_SQL is rated High
This tool executes arbitrary SQL including INSERT, UPDATE, and DELETE operations against data structures. While DELETE operations could be considered Destructive, the tool description emphasizes it as an 'Execute' capability that runs queries with side effects dependent on the SQL arguments provided.
From the tool's definition Execute SQL queries against Google Sheets tables. Supports SELECT, INSERT, UPDATE, and DELETE operations
Risk signalsAccepts freeform code/query input (sql)
Attacks that exploit this kind of access
The rule that runs GOOGLESUPER_EXECUTE_SQL safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Google Super, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For GOOGLESUPER_EXECUTE_SQL, this is the rule to start with:
GOOGLESUPER_EXECUTE_SQL stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Google Super, apply this rule, and every GOOGLESUPER_EXECUTE_SQL call is checked against it from then on.
Questions about GOOGLESUPER_EXECUTE_SQL
Execute SQL queries against Google Sheets tables. Supports SELECT, INSERT, UPDATE, and DELETE operations with familiar SQL syntax. Tables are automatically detected and mapped from the spreadsheet structure. It is categorised as a Execute tool in the Google Super MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
GOOGLESUPER_EXECUTE_SQL accepts 4 parameters: sql, dry_run, delete_method, spreadsheet_id. The full parameter table on this page comes from the server's own tool schema.
Register the Google Super MCP server in PolicyLayer and add a rule for GOOGLESUPER_EXECUTE_SQL: 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 Super. Nothing to install.
GOOGLESUPER_EXECUTE_SQL is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the GOOGLESUPER_EXECUTE_SQL 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 GOOGLESUPER_EXECUTE_SQL. 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.
GOOGLESUPER_EXECUTE_SQL is provided by the Google Super MCP server (googlesuper). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Google Super, and thousands of servers like it.
Across the catalogue