AI agents call check_feature 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 read-only introspection of the Emacs runtime state. It queries whether a feature exists or is loaded without modifying any state, executing code, or causing side effects. This is consistent with the server's stated purpose of providing 'live introspective access' and falls squarely into the Read category (queries data with no side effects).
From the tool's definition Tool name 'check_feature' and description 'Check whether a specific feature is loaded or available' indicate a simple query operation that retrieves status information about loaded features in the Emacs environment.
Attacks that exploit this kind of access
Check whether a specific feature is loaded or available. 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 check_feature: 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.
check_feature 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 check_feature 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 check_feature. 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.
check_feature 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 →