// SCAN REPORT

Imessage-MCP

5 tools. 0 can modify or destroy data without limits.

Read-only server. Low risk, but rate limits prevent runaway API costs.

Last updated: 2 Jul 2026

0 can modify or destroy data

5 read-only

5 tools total

Community server · catalogue entry verified 02/07/2026

How to control Imessage-MCP ↓

TOOL MAP

What Imessage-MCP exposes to your agents

Read (5) Write / Execute (0) Destructive / Financial (0)

Running more than one server? Check your whole stack →

THE RISK

What can go wrong

Even read-only tools carry cost. An agent in a retry loop can make thousands of API calls per minute, exhausting rate limits and running up bills.

POLICY

How to control Imessage-MCP

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

Cap read operations

{
  "get_conversation": {
    "limits": [
      {
        "counter": "get_conversation_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-MCP — 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-MCP →

Instant setup, no code required.

FULL CATALOGUE

All 5 Imessage-MCP tools

READ 5 tools

Read get_conversation get_conversation Read get_recent_messages Show the most recent messages across all conversations (an inbox-style view). Read list_conversations list_conversations Read list_unreplied List conversations whose most recent message was from the other person. Read search_messages search_messages

FAQ

Questions about Imessage-MCP

Is the Imessage- MCP server safe to use without restrictions? +

The Imessage-MCP server is primarily read-only with 5 read tools. While it cannot modify data, an agent in a retry loop can make thousands of API calls per minute, exhausting rate limits and running up costs. Rate limiting is still recommended.

How many tools does the Imessage- MCP server expose? +

5 tools across 1 categories: Read. 5 are read-only. 0 can modify, create, or delete data.

How do I enforce a policy on Imessage-MCP? +

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-MCP tool call.

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

ENFORCE POLICY ON IMESSAGE-MCP →

Instant setup, no code required.

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