send_sticker
Send WhatsApp sticker. Args: to, sticker_url, instance_name, quoted_message_id, delay. Returns: confirmation with message ID.
This record as markdown: /tools/namastexlabs-automagik-tools/send-sticker.md
What send_sticker does on Automagik Tools
AI agents invoke send_sticker to trigger actions in Automagik Tools. 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.
Why send_sticker is rated High
This tool triggers an external operation — sending a WhatsApp message (sticker) to a recipient. It causes a real-world side effect by dispatching a message through WhatsApp to an external party, which classifies it as Execute. Severity is medium because misuse could result in spam or unwanted communication to arbitrary recipients, but it does not modify stored data or commit financial obligations.
From the tool's definition Send WhatsApp sticker... Returns: confirmation with message ID
Attacks that exploit this kind of access
The rule that runs send_sticker safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Automagik Tools, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For send_sticker, this is the rule to start with:
send_sticker 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 Automagik Tools, apply this rule, and every send_sticker call is checked against it from then on.
Questions about send_sticker
Send WhatsApp sticker. Args: to, sticker_url, instance_name, quoted_message_id, delay. Returns: confirmation with message ID. It is categorised as a Execute tool in the Automagik Tools MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Automagik Tools MCP server in PolicyLayer and add a rule for send_sticker: 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 Automagik Tools. Nothing to install.
send_sticker 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 send_sticker 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 send_sticker. 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.
send_sticker is provided by the Automagik Tools MCP server (namastexlabs/automagik-tools). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Automagik Tools, and thousands of servers like it.
Across the catalogue