High Risk →

send_voice

Send a voice message via TTS or pre-recorded audio URL

How to control send_voice ↓

What send_voice does on Mcp Afip

AI agents invoke send_voice 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_voice needs a policy

This tool triggers an external operation — sending a voice message using either text-to-speech synthesis or a pre-recorded audio URL. It initiates an outbound communication action with external side effects. The description doesn't align well with AFIP/tax invoicing context, suggesting it may be misattributed, which lowers confidence slightly.

From the tool's definition Send a voice message via TTS or pre-recorded audio URL

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

How to control send_voice

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_voice:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "send_voice": {
      "limits": [
        {
          "counter": "send_voice_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

send_voice 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_voice

What does the send_voice tool do? +

Send a voice message via TTS or pre-recorded audio URL. 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_voice? +

Register the Mcp Afip MCP server in PolicyLayer and add a rule for send_voice: 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_voice? +

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

Can I rate-limit send_voice? +

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

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

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