Read messages sent to this terminal. Returns all messages and optionally deletes them after reading.
AI agents call get_messages to retrieve information from Mcp Terminal Share without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves/queries messages from a local inter-process communication system. Although it has an optional parameter to delete messages after reading, the core operation is read-based data retrieval. The deletion is reversible within the scope of a running terminal session and requires explicit caller intent.
From the tool's definition Tool description states 'Read messages sent to this terminal' and 'Returns all messages'. The primary function is retrieval with an optional side effect (deletion) that is explicitly under caller control.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Read messages sent to this terminal. Returns all messages and optionally deletes them after reading. It is categorised as a Read tool in the Mcp Terminal Share MCP Server, which means it retrieves data without modifying state.
Register the Mcp Terminal Share MCP server in PolicyLayer and add a rule for get_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 Mcp Terminal Share. Nothing to install.
get_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_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_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_messages is provided by the Mcp Terminal Share MCP server (wu-yu-pei/mcp-terminal-share). 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 →