Read recent messages. Provide EITHER stateId (for state messages) or peerPublicKey (for direct messages). Returns messages with sender info, content, and timestamp. Most recent first.
AI agents call read_messages to retrieve information from Networkselfmd without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves messages from either a state or direct peer communication channel. It performs a query-like operation to fetch historical message data without any side effects—no messages are modified, deleted, or created. The operation is purely informational and non-destructive.
From the tool's definition Tool name is 'read_messages' and description explicitly states it 'Read[s] recent messages' and 'Returns messages with sender info, content, and timestamp.' The verb 'read' and 'returns' indicate retrieval of existing data with no modification, creation, or…
Attacks that exploit this kind of access
Read recent messages. Provide EITHER stateId (for state messages) or peerPublicKey (for direct messages). Returns messages with sender info, content, and timestamp. Most recent first. It is categorised as a Read tool in the Networkselfmd MCP Server, which means it retrieves data without modifying state.
Register the Networkselfmd MCP server in PolicyLayer and add a rule for read_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 Networkselfmd. Nothing to install.
read_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 read_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 read_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.
read_messages is provided by the Networkselfmd MCP server (selfmd/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 →