High 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 Afip

AI agents invoke send_option_list to trigger actions in Mcp Afip. 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.

High Risk

Why send_option_list needs a policy

This tool sends a message via WhatsApp, which constitutes triggering an external operation (outbound communication). It is not a simple data write within a system but an action with external side effects. Severity is medium as it could be misused to send unsolicited messages. Confidence is moderate because the tool description is sparse and its connection to AFIP/electronic invoicing is unclear.

From the tool's definition 'Send an interactive option list (WhatsApp native list)' — triggers an external messaging operation to WhatsApp

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 Afip, 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": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

send_option_list 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.

  1. Create a free account and register Mcp Afip — 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.
RATE-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 Execute tool in the Mcp Afip 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_option_list? +

Register the Mcp Afip 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 Afip. Nothing to install.

What risk level is send_option_list? +

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

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 Afip MCP server (codespar/mcp-dev-latam). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Mcp Afip tool call.

Start from Mcp Afip, 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 Afip 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.