send_audio · Evolution API MCP Server MCP: Risk & Policy

WHAT IT DOES

What send_audio does on Evolution API MCP Server

AI agents use send_audio to create or update resources in Evolution API MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Evolution API MCP Server environment.

WHY IT NEEDS A POLICY

Why send_audio needs a policy

Sending audio messages is a Write operation—it creates and transmits data reversibly (messages can be deleted from chat history by the user or the system). It does not execute arbitrary code, delete data, or involve financial transactions.

From the tool's definition Tool name 'send_audio' combined with sibling tools 'send_text_message', 'send_image', and 'send_document' which clearly create message content. The server description states it enables users to 'send messages' and 'manage media'.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

send_audio Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "send_audio": {
      "limits": [
        {
          "counter": "send_audio_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Evolution API MCP Server, so you can run agents against it safely.

FAQ

Questions about send_audio

What does the send_audio tool do? +

send_audio. It is categorised as a Write tool in the Evolution API MCP Server 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_audio? +

Register the Evolution API MCP Server MCP server in PolicyLayer and add a rule for send_audio: 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 Evolution API MCP Server. Nothing to install.

What risk level is send_audio? +

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

Can I rate-limit send_audio? +

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

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

send_audio is provided by the Evolution API MCP Server MCP server (pablobispo/evoapi-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

send_audio is one line of Evolution API MCP Server's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →