AI agents use send-files to create or update resources in iMessage MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your iMessage MCP Server environment.
This tool creates new iMessage data (outbound message objects with file attachments) and modifies the conversation state by adding sent messages. The action is reversible in principle (users can delete sent messages), so it is Write rather than Execute or Destructive.
From the tool's definition Tool name 'send-files' and description 'Send multiple files to a recipient' indicate data modification. The server description confirms the tool operates within iMessage, enabling message/file sending capabilities.
Documented attack patterns abuse exactly the kind of access send-files gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and iMessage MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for send-files:
{
"version": "1",
"default": "deny",
"tools": {
"send-files": {
"limits": [
{
"counter": "send-files_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}send-files 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.
Free to start. No card required.
Send multiple files to a recipient. It is categorised as a Write tool in the iMessage MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the iMessage MCP Server MCP server in PolicyLayer and add a rule for send-files: 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 iMessage MCP Server. Nothing to install.
send-files is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the send-files 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.
Set action: deny in the PolicyLayer policy for send-files. 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.
send-files is provided by the iMessage MCP Server MCP server (sameelarif/imessage-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from iMessage MCP Server, 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.
14 iMessage MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.