Get the current state of the active combat encounter.
AI agents call get_encounter_state 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 and returns information about the current combat encounter state in an RPG game session. It has no side effects—it does not create, modify, delete, or execute anything. The information returned helps an AI agent understand the game state to make informed decisions, but the act of querying itself causes no changes to the game world or data structure.
From the tool's definition Tool name 'get_encounter_state' and description 'Get the current state of the active combat encounter' indicate a query operation that retrieves data about game state without modifying, deleting, or executing external operations.
Documented attack patterns abuse exactly the kind of access get_encounter_state 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 get_encounter_state:
{
"version": "1",
"default": "deny",
"tools": {
"get_encounter_state": {}
}
}get_encounter_state 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 the current state of the active combat encounter. 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 get_encounter_state: 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.
get_encounter_state 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_encounter_state 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_encounter_state. 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_encounter_state 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.