send_image · Evolution API MCP Server MCP: Risk & Policy

WHAT IT DOES

What send_image does on Evolution API MCP Server

AI agents use send_image 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_image needs a policy

This tool sends/creates image messages to WhatsApp contacts. Sending messages is a reversible write operation—messages can be deleted or chats cleared. While it affects external communication (WhatsApp), it does not execute arbitrary code, delete data irreversibly, or move money. The empty description lowers confidence slightly, but the name and server context make the Write category clear.

From the tool's definition Tool name 'send_image' and server context 'send messages' indicate the tool creates/sends media content. Sibling tools include 'send_text_message', 'send_audio', 'send_document' which are clearly Write operations.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

send_image Rate-limited

send_image 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_image": {
      "limits": [
        {
          "counter": "send_image_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_image

What does the send_image tool do? +

send_image. 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_image? +

Register the Evolution API MCP Server MCP server in PolicyLayer and add a rule for send_image: 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_image? +

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

Can I rate-limit send_image? +

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

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

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