Delete a chart from a Google Sheets spreadsheet
AI agents call sheets_delete_chart to permanently remove resources in MCP Google Sheets Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes a chart object from a spreadsheet. Chart deletion cannot be undone by the tool itself (undo would require a separate operation or manual intervention). Deleting a chart is a destructive action that destroys data visualization and cannot be reverted through the tool's API.
From the tool's definition Tool name is 'sheets_delete_chart' with description 'Delete a chart from a Google Sheets spreadsheet'. The verb 'Delete' is explicit and irreversible.
Attacks that exploit this kind of access
Delete a chart from a Google Sheets spreadsheet. It is categorised as a Destructive tool in the MCP Google Sheets Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the MCP Google Sheets Server MCP server in PolicyLayer and add a rule for sheets_delete_chart: 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 MCP Google Sheets Server. Nothing to install.
sheets_delete_chart is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the sheets_delete_chart 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 sheets_delete_chart. 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.
sheets_delete_chart is provided by the MCP Google Sheets Server MCP server (oregpt/agenticledger_mcp_sheetsonly). 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 →