AI agents call search_source 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 reads and searches source code files using regex patterns. It has no side effects, does not modify data, execute code, or trigger external operations. It is purely a retrieval/query function similar to grep. The low severity reflects that source code search poses minimal risk even if misused by an agent.
From the tool's definition Tool performs 'Search RimWorld source code using regex' — a query operation that retrieves matching code snippets without modifying or executing anything.
Documented attack patterns abuse exactly the kind of access search_source 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_source:
{
"version": "1",
"default": "deny",
"tools": {
"search_source": {}
}
}search_source 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 RimWorld source code using regex. 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_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 RimSage. Nothing to install.
search_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 search_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 search_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.
search_source 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.