Add a new chatter to the database
AI agents use add_chatter to create or update resources in Google Tag Manager MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Google Tag Manager MCP Server environment.
This tool creates or adds data to a database without permanent deletion or external system side effects. It is reversible (the entry can be deleted via 'delete_chatter' which exists as a sibling tool). The context of Google Tag Manager suggests this likely adds a chat/communication record.
From the tool's definition Tool name 'add_chatter' and description 'Add a new chatter to the database' indicate a create operation that modifies data reversibly by inserting a new record.
Attacks that exploit this kind of access
Add a new chatter to the database. It is categorised as a Write tool in the Google Tag Manager MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Google Tag Manager MCP Server MCP server in PolicyLayer and add a rule for add_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.
add_chatter is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the add_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 add_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.
add_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 →