// SCAN REPORT

Imessage

4 tools. 1 can modify or destroy data without limits.

1 write tool that can modify data. Rate limits recommended.

Last updated: 3 Jul 2026

1 can modify or destroy data

3 read-only

4 tools total

Community server · catalogue entry verified 03/07/2026

How to control Imessage ↓

TOOL MAP

What Imessage exposes to your agents

Read (3) Write / Execute (1) Destructive / Financial (0)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous Imessage tools

Write · High send_message The tool name 'send_message' clearly indicates message creation/transmission, which is a Write operation (creates new data reversibly).

1 of Imessage's 4 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Imessage

PolicyLayer is an MCP gateway — it sits between your AI agents and Imessage, and nothing reaches the server without passing your rules. These are the rules we recommend:

Rate limit write operations

{
  "send_message": {
    "limits": [
      {
        "counter": "send_message_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "list_chats": {
    "limits": [
      {
        "counter": "list_chats_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Imessage — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON IMESSAGE →

Instant setup, no code required.

FULL CATALOGUE

All 4 Imessage tools

WRITE 1 tools

Write send_message send_message

READ 3 tools

Read list_chats List the most recent iMessage conversations. Read read_messages Read recent messages from a specific chat, oldest first. Read search_messages Substring-search message text across all chats (case-insensitive).

FAQ

Questions about Imessage

How do I prevent bulk modifications through Imessage? +

The Imessage server has 1 write tools including send_message. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Imessage.

How many tools does the Imessage MCP server expose? +

4 tools across 2 categories: Read, Write. 3 are read-only. 1 can modify, create, or delete data.

How do I enforce a policy on Imessage? +

Register the Imessage MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Imessage tool call.

Deterministic rules across all 4 Imessage tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON IMESSAGE →

Instant setup, no code required.

4 Imessage tools catalogued and risk-classified — across an index of 43,000+ MCP servers.