Create a spatial node network such as a town, road, or dungeon.
AI agents use create_node_network 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 generates new game world data structures that are persisted in the SQLite backend. It is reversible (nodes can be deleted or modified in future turns), so it does not meet the Destructive threshold. It does not execute arbitrary code or trigger external systems (Execute), nor does it move financial resources (Financial).
From the tool's definition The tool 'create_node_network' creates spatial structures (towns, roads, dungeons) within the game world. The verb 'create' indicates data generation and modification.
Documented attack patterns abuse exactly the kind of access create_node_network 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 create_node_network:
{
"version": "1",
"default": "deny",
"tools": {
"create_node_network": {
"limits": [
{
"counter": "create_node_network_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} create_node_network 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 spatial node network such as a town, road, or dungeon. 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 create_node_network: 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.
create_node_network 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 create_node_network 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 create_node_network. 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.
create_node_network 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.