Subscribe to real-time events on world or combat topics. Events sent as JSON-RPC notifications.
AI agents call subscribe_to_events 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.
Subscribing to events is a read/listen operation — it registers interest in receiving notifications but does not modify, delete, execute, or financially affect any data. The tool passively receives JSON-RPC notifications about game state changes rather than causing them. Severity is low because misuse would at most result in unnecessary subscriptions or information disclosure within the game engine context.
From the tool's definition Subscribe to real-time events on world or combat topics. Events sent as JSON-RPC notifications.
Documented attack patterns abuse exactly the kind of access subscribe_to_events 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 subscribe_to_events:
{
"version": "1",
"default": "deny",
"tools": {
"subscribe_to_events": {}
}
}subscribe_to_events 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.
Subscribe to real-time events on world or combat topics. Events sent as JSON-RPC notifications. 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 subscribe_to_events: 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.
subscribe_to_events 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 subscribe_to_events 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 subscribe_to_events. 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.
subscribe_to_events 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.