Atualiza as informações de um grupo específico na Zappaz API
AI agents use update_group to create or update resources in Zappaz MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Zappaz MCP Server environment.
The tool creates or modifies group data (settings, name, description, etc.) within WhatsApp via the Zappaz API. These changes are reversible and do not delete data or execute arbitrary code. While it affects communication channels, the impact is limited to group configuration rather than destructive actions or financial transactions.
From the tool's definition Tool name is 'update_group' and description states 'Atualiza as informações de um grupo específico na Zappaz API' (Updates information of a specific group in the Zappaz API). This modifies group metadata reversibly.
Attacks that exploit this kind of access
Atualiza as informações de um grupo específico na Zappaz API. It is categorised as a Write tool in the Zappaz MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Zappaz MCP Server MCP server in PolicyLayer and add a rule for update_group: 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 Zappaz MCP Server. Nothing to install.
update_group 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 update_group 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 update_group. 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.
update_group is provided by the Zappaz MCP Server MCP server (viiniolliveira/zappaz-mcp). 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 →