AI agents call library_source 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 retrieves and displays existing source code from an Emacs library without executing it, modifying it, or causing side effects. It is a read-only operation equivalent to viewing a file or querying documentation. While the source code could theoretically be analyzed for vulnerabilities, the tool itself performs no action beyond retrieval, placing it squarely in the Read category with low severity.
From the tool's definition Tool description states it 'Return[s] the full source code of an Elisp library' — a retrieval operation with no modification or execution capability.
Attacks that exploit this kind of access
Return the full source code of an Elisp library. 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 library_source: 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.
library_source 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 library_source 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 library_source. 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.
library_source 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 →