Create a persistent room with immutable description. Optionally links to previous room.
AI agents use generate_room_node to create or update resources in Rpg — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Rpg environment.
This tool creates new game world data (rooms) that is persisted to the SQLite database. Creation is reversible (rooms can be deleted or overwritten in a typical game engine), so it qualifies as Write rather than Destructive.
From the tool's definition Tool 'generate_room_node' description states it will 'Create a persistent room' - the verb 'create' indicates data creation.
Documented attack patterns abuse exactly the kind of access generate_room_node 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 generate_room_node:
{
"version": "1",
"default": "deny",
"tools": {
"generate_room_node": {
"limits": [
{
"counter": "generate_room_node_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} generate_room_node stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Create a persistent room with immutable description. Optionally links to previous room. It is categorised as a Write tool in the Rpg MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Rpg MCP server in PolicyLayer and add a rule for generate_room_node: 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.
generate_room_node is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the generate_room_node 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 generate_room_node. 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.
generate_room_node 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.