send_sticker

THE RISK

High Risk

Why send_sticker needs a policy

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

Documented attack patterns abuse exactly the kind of access send_sticker gives an agent:

POLICY

How to control send_sticker

PolicyLayer is an MCP gateway — it sits between your AI agents and Automagik Tools, and nothing reaches the server without passing your rules. This is the rule we recommend for send_sticker:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "send_sticker": {
      "limits": [
        {
          "counter": "send_sticker_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

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.

Create a free account and register Automagik Tools — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Automagik Tools tools

Destructive delete_agent_conversation Delete a conversation session with an agent. This cannot be undone. Destructive delete_credential Delete a stored credential. Destructive delete_message Delete message for everyone. Only works for messages from you (from_me=True), within ~48 h Destructive delete_schedule Delete a schedule. Destructive delete_source Delete a workflow source. Destructive delete_task Delete a task execution. Destructive delete_team_collaboration Delete a team collaboration session. This cannot be undone. Destructive delete_workflow Delete a synchronized workflow.

All 122 Automagik Tools tools →

Execute tools on other servers

Android Forensics ADB MCP Server adb_shell_command EMBA-MCP run_emba_scan Frida Game Hacking MCP remove_breakpoint Procmon request_elevation

Go deeper

High-risk tools in Automagik Tools → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Agent sandbox → Bounding what an agent can execute and where the boundary should sit.
Least privilege for MCP → Granting agents the minimum tool surface the task needs.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about send_sticker

What does the send_sticker tool do? +

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.

How do I enforce a policy on send_sticker? +

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.

What risk level is send_sticker? +

send_sticker is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit send_sticker? +

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.

How do I block send_sticker completely? +

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.

What MCP server provides send_sticker? +

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.

Enforce policy on every Automagik Tools tool call.

Start from Automagik Tools, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →