AI agents call list_manuals to retrieve information from Ragmacs without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only operation—it queries and returns a list of available manual names from the Emacs Info system. There are no side effects, no code execution, no data modification, and no external operations triggered. The blast radius of misuse is minimal, as an agent could only enumerate available manuals without accessing their contents or affecting the system.
From the tool's definition Tool name 'list_manuals' and description 'Return a list of available Info manual names' indicate a query operation that retrieves information without modification or execution.
Attacks that exploit this kind of access
Return a list of available Info manual names. It is categorised as a Read tool in the Ragmacs MCP Server, which means it retrieves data without modifying state.
Register the Ragmacs MCP server in PolicyLayer and add a rule for list_manuals: 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 Ragmacs. Nothing to install.
list_manuals 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 list_manuals 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 list_manuals. 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.
list_manuals is provided by the Ragmacs MCP server (landermkerbey/ragmacs-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 →