List recently used folder paths for a machine. Useful for starting sessions in familiar locations.
AI agents call happy_list_recent_paths 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 historical data about folder paths without side effects. It cannot modify, delete, or execute operations. The information returned (folder paths) is benign and useful for navigation context. Blast radius is minimal—an AI agent could only learn about directory structure, not cause harm.
From the tool's definition Tool name and description indicate it 'list[s] recently used folder paths' with no modification, deletion, or execution capability. This is a read-only query operation.
Attacks that exploit this kind of access
List recently used folder paths for a machine. Useful for starting sessions in familiar locations. 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_list_recent_paths: 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_list_recent_paths 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_list_recent_paths 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_list_recent_paths. 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_list_recent_paths 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 →