Medium Risk

send_document

Send a document via WhatsApp

How to control send_document ↓

What send_document does on Mcp Ap2

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

Medium Risk

Why send_document needs a policy

This tool sends documents via WhatsApp, which is a write operation (creates/transmits data). It is not destructive (documents can be retracted or resent), not financial (no money movement), and not execute (no arbitrary code/command execution). Severity is medium rather than low because sending unsolicited or incorrect documents could have reputational or compliance implications, but the operation is reversible.

From the tool's definition Tool description states 'Send a document via WhatsApp' — this performs an action that creates/transmits a message or document, which is a reversible write operation. The tool modifies state by delivering a document through an external channel.

Documented attack patterns abuse exactly the kind of access send_document gives an agent:

How to control send_document

PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Ap2, and nothing reaches the server without passing your rules. This is the rule we recommend for send_document:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "send_document": {
      "limits": [
        {
          "counter": "send_document_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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

  1. Create a free account and register Mcp Ap2 — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about send_document

What does the send_document tool do? +

Send a document via WhatsApp. It is categorised as a Write tool in the Mcp Ap2 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_document? +

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

What risk level is send_document? +

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

Can I rate-limit send_document? +

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

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

send_document is provided by the Mcp Ap2 MCP server (@codespar/mcp-ap2). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Mcp Ap2 tool call.

Start from Mcp Ap2, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

1300 Mcp Ap2 tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.