World map operations - viewing, rendering, and modification. Actions: overview, region, tiles, patch, preview, find_poi, suggest_poi Aliases: summary→overview, grid→tiles, apply→patch, dry_run→preview, locate→find_poi 🗺️ MAP WORKFLOW: 1. overview - Get high-level world stats 2. region - View spe...
AI agents use world_map 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.
The tool combines read operations (overview, region, tiles, find_poi) with write/modification operations (patch, preview). Since the most severe applicable category must be chosen, and 'patch' applies DSL script modifications to the world map (a persistent SQLite-backed world state), this qualifies as Write.
From the tool's definition 'World map operations - viewing, rendering, and modification' and actions include 'patch - Apply modifications via DSL script' and 'preview - Preview changes before applying'
Documented attack patterns abuse exactly the kind of access world_map 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_map:
{
"version": "1",
"default": "deny",
"tools": {
"world_map": {
"limits": [
{
"counter": "world_map_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} world_map 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.
World map operations - viewing, rendering, and modification. Actions: overview, region, tiles, patch, preview, find_poi, suggest_poi Aliases: summary→overview, grid→tiles, apply→patch, dry_run→preview, locate→find_poi 🗺️ MAP WORKFLOW: 1. overview - Get high-level world stats 2. region - View specific region details 3. tiles - Get full tile grid for rendering 4. find_poi - Find valid POI placement locations 5. patch - Apply modifications via DSL script 6. preview - Preview changes before applying For world creation/management, use world_manage 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_map: 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_map 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_map 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_map. 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_map 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.