Delete a chatter from the database
AI agents call delete_chatter to permanently remove resources in Google Tag Manager MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes data from a database without the ability to undo the action. Although 'chatter' is a relatively minor data entity compared to configuration records, any deletion from a database is irreversible and falls under the Destructive category.
From the tool's definition Tool name contains 'delete' and description states 'Delete a chatter from the database'. The verb 'delete' combined with database removal indicates irreversible data destruction.
Attacks that exploit this kind of access
Delete a chatter from the database. It is categorised as a Destructive tool in the Google Tag Manager MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Google Tag Manager MCP Server MCP server in PolicyLayer and add a rule for delete_chatter: 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 Tag Manager MCP Server. Nothing to install.
delete_chatter 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 delete_chatter 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 delete_chatter. 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.
delete_chatter is provided by the Google Tag Manager MCP Server MCP server (neep305/mcp-for-gtm). 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 →