send_file

Send a file attachment via iMessage/SMS. Requires absolute file path and recipient handle.

SERVERAirMCP SOURCEairmcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/heznpc-airmcp/send-file.md

WHAT IT DOES

What send_file does on AirMCP

AI agents invoke send_file to trigger actions in AirMCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

RISK

Why send_file is rated High

This tool sends an iMessage or SMS with a file attachment to an external recipient. It triggers an external communication action (message delivery) whose effects depend on the arguments (file path and recipient). Sending data to third parties is not merely a Write (local data modification) but an Execute-level operation that dispatches content outside the system.

From the tool's definition Send a file attachment via iMessage/SMS. Requires absolute file path and recipient handle.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs send_file safely

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

send_file Rate-limited

send_file stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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": {
      "limits": [
        {
          "counter": "send_file_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about send_file

What does the send_file tool do? +

Send a file attachment via iMessage/SMS. Requires absolute file path and recipient handle. It is categorised as a Execute tool in the AirMCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on send_file? +

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

What risk level is send_file? +

send_file is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit send_file? +

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

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

send_file is provided by the Air MCP server (airmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Air, and thousands of servers like it.

This server

All 279 Air tools → High-risk tools on this server →

Across the catalogue

send_key_to_window on Frida Game Hacking MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →