Load a combat encounter from the database.
AI agents call load_encounter to retrieve information from Rpg without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves/queries an existing encounter from persistent storage. The verb 'load' and the absence of any language suggesting creation, modification, deletion, or execution of game logic indicate a read-only operation. The blast radius is minimal since it only exposes already-stored game state without side effects. No financial, destructive, or executable operations are performed.
From the tool's definition Tool name 'load_encounter' and description 'Load a combat encounter from the database' indicate a retrieval operation with no modification of data.
Documented attack patterns abuse exactly the kind of access load_encounter gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Rpg, and nothing reaches the server without passing your rules. This is the rule we recommend for load_encounter:
{
"version": "1",
"default": "deny",
"tools": {
"load_encounter": {}
}
}load_encounter 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.
Load a combat encounter from the database. It is categorised as a Read tool in the Rpg MCP Server, which means it retrieves data without modifying state.
Register the Rpg MCP server in PolicyLayer and add a rule for load_encounter: 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 Rpg. Nothing to install.
load_encounter 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 load_encounter 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 load_encounter. 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.
load_encounter is provided by the Rpg MCP server (mnehmos/mnehmos.rpg.mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Rpg, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
47 Rpg tools catalogued and risk-classified — across an index of 43,000+ MCP servers.