AI agents call function_completions 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 only reads and retrieves function name completions from the Emacs environment. It has no side effects, cannot modify data, and poses minimal risk even if misused by an AI agent. It fits the Read category: retrieves or queries data with no side effects (similar to search, list, get operations). The low severity reflects that incorrect use would only return unwanted completion suggestions, not cause harm.
From the tool's definition Tool returns function names matching a prefix - a query operation that retrieves data without modifying any state. Description explicitly uses 'Return' and 'matching a prefix', indicating a lookup/search function.
Attacks that exploit this kind of access
Return all function names matching a prefix using orderless. 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 function_completions: 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.
function_completions 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 function_completions 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 function_completions. 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.
function_completions 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 →