create_instance · Evolution API WhatsApp MCP Server MCP

WHAT IT DOES

What create_instance does on Evolution API WhatsApp MCP Server

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

WHY IT NEEDS A POLICY

Why create_instance needs a policy

This tool creates a new WhatsApp Business instance, which is a reversible write operation. It establishes a new communication channel/resource but does not delete data, execute arbitrary code, or move money. The severity is medium because an agent could create many instances consuming resources or establish unauthorized communication channels, but the action is reversible via delete_instance.

From the tool's definition Tool name 'create_instance' combined with description 'Create a new WhatsApp instance' indicates creation of a new resource. Server description confirms it supports 'creating instances' as a core capability.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_instance Rate-limited

create_instance 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": {
    "create_instance": {
      "limits": [
        {
          "counter": "create_instance_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 WhatsApp MCP Server, so you can run agents against it safely.

FAQ

Questions about create_instance

What does the create_instance tool do? +

Create a new WhatsApp instance. It is categorised as a Write tool in the Evolution API WhatsApp 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 create_instance? +

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

What risk level is create_instance? +

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

Can I rate-limit create_instance? +

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

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

create_instance is provided by the Evolution API WhatsApp MCP Server MCP server (luiso2/mcp-evolution-api). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.