Read recent messages from a Happy AI session. Use this to see the conversation history.
AI agents call happy_read_messages to retrieve information from Happy Server MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves conversation history from an existing AI session without creating, modifying, deleting, or executing any actions. It is purely informational and has no side effects on the session or system state. The low severity reflects minimal blast radius — an agent reading messages cannot cause damage or unintended operations.
From the tool's definition Tool name contains 'read' and description states 'Read recent messages from a Happy AI session. Use this to see the conversation history' — explicit read-only operation with no modification capability.
Attacks that exploit this kind of access
Read recent messages from a Happy AI session. Use this to see the conversation history. It is categorised as a Read tool in the Happy Server MCP MCP Server, which means it retrieves data without modifying state.
Register the Happy Server MCP server in PolicyLayer and add a rule for happy_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 Happy Server MCP. Nothing to install.
happy_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 happy_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 happy_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.
happy_read_messages is provided by the Happy Server MCP server (zhigang1992/happy-server-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 →