AI agents call get_def_details 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 returns data (XML definitions) from the RimWorld source code without any capability to create, modify, delete, or execute operations. It is a pure read/query operation with no side effects, matching the 'Read' category definition.
From the tool's definition Tool name 'get_def_details' and description 'Get XML of a Def' indicate retrieval of data without modification. The verb 'Get' and context of 'XML of a Def' (RimWorld definition files) show a read-only query operation.
Documented attack patterns abuse exactly the kind of access get_def_details 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 get_def_details:
{
"version": "1",
"default": "deny",
"tools": {
"get_def_details": {}
}
}get_def_details 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.
Get XML of a Def. 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 get_def_details: 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.
get_def_details 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 get_def_details 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 get_def_details. 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.
get_def_details 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.