Show the most recent messages across all conversations (an inbox-style view).
AI agents call get_recent_messages to retrieve information from Imessage-MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays message data without any side effects. It is a read operation that queries recent messages in an inbox-style view. The server explicitly advertises read-only access, and the sibling tools (get_conversation, list_conversations, list_unreplied, search_messages) are all read operations. No data is created, modified, or deleted.
From the tool's definition Tool name 'get_recent_messages' and server description states 'Read-only access to imessage'. The tool retrieves recent messages without modifying data.
Attacks that exploit this kind of access
Show the most recent messages across all conversations (an inbox-style view). It is categorised as a Read tool in the Imessage-MCP MCP Server, which means it retrieves data without modifying state.
Register the Imessage- MCP server in PolicyLayer and add a rule for get_recent_messages: 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. Nothing to install.
get_recent_messages is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_recent_messages 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 get_recent_messages. 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.
get_recent_messages is provided by the Imessage- MCP server (joshkaplan-dev/imessage-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →