check_messages
AI agents call check_messages to retrieve information from Universal AI Chat MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name and context strongly indicate it retrieves message data without modification or side effects. The pattern of sibling tools (get_*, list_*) confirms this server primarily exposes Read operations for communication and context sharing. No evidence suggests code execution, data deletion, or financial operations. Severity is low because reading messages poses minimal risk even if misused by an agent.
From the tool's definition Tool name 'check_messages' suggests retrieving or polling messages; consistent with sibling tools like 'get_conversation', 'get_shared_context', and 'get_my_session_info' which are all Read operations. Description is empty, reducing confidence slightly.
Attacks that exploit this kind of access
check_messages. It is categorised as a Read tool in the Universal AI Chat MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Universal AI Chat MCP Server MCP server in PolicyLayer and add a rule for check_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 Universal AI Chat MCP Server. Nothing to install.
check_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 check_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 check_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.
check_messages is provided by the Universal AI Chat MCP Server MCP server (marc-shade/universal-ai-chat). 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 →