Manage RPG worlds - creation, retrieval, and procedural generation. Actions: create, get, list, delete, update (environment), generate (procedural), get_state Aliases: new→create, fetch→get, all→list, remove→delete, set→update, gen→generate, state→get_state 🌍 WORLD WORKFLOW: 1. generate - Create...
AI agents use world_manage 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 modifies game state reversibly through create, update, and delete operations on world objects stored in SQLite. While it includes a delete action, context indicates this is game world management (not system-level destruction), and the effects are recoverable by recreating worlds.
From the tool's definition Tool performs create, update, delete, and generate actions on RPG world data. Description explicitly states 'creation, retrieval, and procedural generation' with aliases showing create→new, delete→remove, update→set.
Documented attack patterns abuse exactly the kind of access world_manage 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 world_manage:
{
"version": "1",
"default": "deny",
"tools": {
"world_manage": {
"limits": [
{
"counter": "world_manage_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}world_manage 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.
Manage RPG worlds - creation, retrieval, and procedural generation. Actions: create, get, list, delete, update (environment), generate (procedural), get_state Aliases: new→create, fetch→get, all→list, remove→delete, set→update, gen→generate, state→get_state 🌍 WORLD WORKFLOW: 1. generate - Create procedural world with terrain/biomes 2. get_state - Check world status 3. update - Set time/weather/season 4. For map operations, use world_map tool instead. 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 world_manage: 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.
world_manage 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 world_manage 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 world_manage. 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.
world_manage 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.