whatsapp_send_file

SERVERLocal SOURCElocal-mcp

Medium RISK CLASS

Category Write

Parameters 42 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-local-mcp-local-mcp/whatsapp-send-file.md

WHAT IT DOES

What whatsapp_send_file does on Local

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

Parameter	Type	Required	Description
`caption`	string	—	Optional caption text to accompany the file
`chat_id`	string	Yes	Chat ID from whatsapp_list_chats
`confirm`	boolean	—	Must be true to actually send. Without it, returns a preview.
`file_path`	string	Yes	Absolute path to the local file to send

Parameters from the server's own tool schema.

RISK

Why whatsapp_send_file is rated Medium

The tool creates and sends file attachments to WhatsApp chats, which is a persistent write operation that modifies external communication state. While not destructive (messages can technically be deleted) or financial, it represents a high-severity write because: (1) sends data to external parties via an unofficial client with ToS violation risks, (2) affects user communication and potentially exposes files to…

From the tool's definition Tool description explicitly states "This is a write operation" and "set confirm=true to actually send", indicating irreversible creation of messages in WhatsApp chats. File attachments are sent to external communication platform.

Risk signalsAccepts file system path (file_path)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs whatsapp_send_file safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Local, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For whatsapp_send_file, this is the rule to start with:

whatsapp_send_file Rate-limited

whatsapp_send_file 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": {
    "whatsapp_send_file": {
      "limits": [
        {
          "counter": "whatsapp_send_file_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Local, apply this rule, and every whatsapp_send_file call is checked against it from then on.

FAQ

Questions about whatsapp_send_file

What does the whatsapp_send_file tool do? +

Sends a file attachment to a WhatsApp chat. The chat_id MUST come from a previous whatsapp_list_chats call — never fabricate IDs. file_path must be an absolute path to a local file. This is a write operation: the first call (confirm=false) returns a preview without sending; set confirm=true to actually send. ⚠️ Uses Wacli (unofficial WhatsApp client). Accounts may be restricted for ToS violations. It is categorised as a Write tool in the Local MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does whatsapp_send_file accept? +

whatsapp_send_file accepts 4 parameters: caption, chat_id, confirm, file_path. Required: chat_id, file_path. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on whatsapp_send_file? +

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

What risk level is whatsapp_send_file? +

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

Can I rate-limit whatsapp_send_file? +

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

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

whatsapp_send_file is provided by the Local MCP server (local-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Local, and thousands of servers like it.

This server

All 234 Local tools →

Across the catalogue

sms_send on Twilio SMS MCP Server →send-draft on Meme MCP Server →mail_send_draft on Apple Apps MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →