Medium Risk

send_option_list

Send an interactive option list (WhatsApp native list). Does NOT work in groups.

How to control send_option_list ↓

What send_option_list does on Mcp Ap2

AI agents use send_option_list to create or update resources in Mcp Ap2 — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Ap2 environment.

Medium Risk

Why send_option_list needs a policy

The action creates/transmits a message artifact (interactive option list) that modifies communication state and user interaction flow. It does not delete data (Destructive), execute arbitrary code (Execute), move money (Financial), or merely read data (Read).

From the tool's definition Tool sends/transmits a list interaction via WhatsApp; 'send' indicates outbound communication creation. As part of AP2 payment protocol suite with related tools like 'accept_dispute', 'activate_subscription', this appears designed for transactional workflows…

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

How to control send_option_list

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

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "send_option_list": {
      "limits": [
        {
          "counter": "send_option_list_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

send_option_list stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Mcp Ap2 — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about send_option_list

What does the send_option_list tool do? +

Send an interactive option list (WhatsApp native list). Does NOT work in groups. It is categorised as a Write tool in the Mcp Ap2 MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on send_option_list? +

Register the Mcp Ap2 MCP server in PolicyLayer and add a rule for send_option_list: 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 Mcp Ap2. Nothing to install.

What risk level is send_option_list? +

send_option_list is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit send_option_list? +

Yes. Add a rate_limit block to the send_option_list 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_option_list completely? +

Set action: deny in the PolicyLayer policy for send_option_list. 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_option_list? +

send_option_list is provided by the Mcp Ap2 MCP server (@codespar/mcp-ap2). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Mcp Ap2 tool call.

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

Free to start. No card required.

1300 Mcp Ap2 tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.