list_rooms

THE RISK

Low Risk

Why list_rooms needs a policy

This tool retrieves or queries existing game world data (rooms in the spatial graph) without creating, modifying, deleting, or executing any operations. It is purely informational and read-only, making it the least risky category.

From the tool's definition Tool name 'list_rooms' and description 'List all rooms in the spatial graph. Optionally filter by biome' indicate a query/retrieval operation with no side effects.

Documented attack patterns abuse exactly the kind of access list_rooms gives an agent:

POLICY

How to control list_rooms

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 list_rooms:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_rooms": {}
  }
}

list_rooms is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Rpg — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Rpg tools

Execute improvisation_manage Manage improvised actions, custom effects, and arcane synthesis. Actions: stunt, apply_eff Execute execute_lair_action Execute a lair action at initiative 20 when isLairActionPending is true. Apply environment Execute concentration_manage Manage spell concentration (D&D 5e rules). 🎯 WHEN TO USE: - After damage: check_save (CO Execute roll_death_save Roll a d20 death saving throw for a character at 0 HP. 10+ success, nat 20 regains 1 HP, n Execute turn_manage Turn-based strategy game lifecycle (multi-agent coordination). 🎮 STRATEGY TURN CYCLE: 1. Write world_map World map operations - viewing, rendering, and modification. Actions: overview, region, ti Write advance_turn Advance to the next combatant\ Write agent_manage Manage LLM-driven NPCs (

All 47 Rpg tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about list_rooms

What does the list_rooms tool do? +

List all rooms in the spatial graph. Optionally filter by biome. It is categorised as a Read tool in the Rpg MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_rooms? +

Register the Rpg MCP server in PolicyLayer and add a rule for list_rooms: 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.

What risk level is list_rooms? +

list_rooms is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_rooms? +

Yes. Add a rate_limit block to the list_rooms 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.

How do I block list_rooms completely? +

Set action: deny in the PolicyLayer policy for list_rooms. 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.

What MCP server provides list_rooms? +

list_rooms 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.

Enforce policy on every Rpg tool call.

Start from Rpg, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →