send_file_to_opened_session · Wati MCP: Risk & Policy

WHAT IT DOES

What send_file_to_opened_session does on Wati

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

WHY IT NEEDS A POLICY

Why send_file_to_opened_session needs a policy

This tool creates or transmits data (a file/media object) to a WhatsApp session, which is a reversible Write operation. It does not execute arbitrary code, delete data, or move money. The empty description lowers confidence slightly, but context from the server's purpose (WATI WhatsApp Business API for messaging and media handling) and sibling tools strongly indicates file transmission.

From the tool's definition Tool name 'send_file_to_opened_session' indicates sending/uploading file content to an active WhatsApp session. The server description confirms it handles 'media' and messaging capabilities.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

send_file_to_opened_session Rate-limited

send_file_to_opened_session 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_file_to_opened_session": {
      "limits": [
        {
          "counter": "send_file_to_opened_session_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 Wati, so you can run agents against it safely.

FAQ

Questions about send_file_to_opened_session

What does the send_file_to_opened_session tool do? +

send_file_to_opened_session. It is categorised as a Write tool in the Wati 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_file_to_opened_session? +

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

What risk level is send_file_to_opened_session? +

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

Can I rate-limit send_file_to_opened_session? +

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

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

send_file_to_opened_session is provided by the Wati MCP server (jairajmehra/wati_whatsapp_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.