AI agents call search_defs to retrieve information from RimSage without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries data from RimWorld source code definitions without creating, modifying, deleting, or executing any operations. It is a search/lookup function with no side effects, fitting clearly into the Read category. Low severity because misuse would only expose information already present in the codebase.
From the tool's definition Tool performs search operations on Def indices by partial name or label; returns query results without modification.
Documented attack patterns abuse exactly the kind of access search_defs gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and RimSage, and nothing reaches the server without passing your rules. This is the rule we recommend for search_defs:
{
"version": "1",
"default": "deny",
"tools": {
"search_defs": {}
}
}search_defs is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Search Def indices by partial name or label. It is categorised as a Read tool in the RimSage MCP Server, which means it retrieves data without modifying state.
Register the RimSage MCP server in PolicyLayer and add a rule for search_defs: 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 RimSage. Nothing to install.
search_defs 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 search_defs 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 search_defs. 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.
search_defs is provided by the RimSage MCP server (realloon/rimsage). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 6 RimSage tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
6 RimSage tools catalogued and risk-classified — across an index of 42,500+ MCP servers.