Low Risk

get_world_state

Retrieves the current state of the generated world.

How to control get_world_state ↓

What get_world_state does on Rpg

AI agents call get_world_state to retrieve information from Rpg without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why get_world_state needs a policy

This tool retrieves data about the RPG world state without creating, modifying, deleting, or executing any operations. It is a simple query function analogous to 'get' or 'fetch' operations. The blast radius of misuse is minimal—an AI agent querying world state cannot cause harm to game mechanics, player progress, or external systems. Classification as Read is appropriate.

From the tool's definition Tool name 'get_world_state' and description 'Retrieves the current state of the generated world' indicate a read-only query operation with no side effects.

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

How to control get_world_state

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

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_world_state": {}
  }
}

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

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

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_world_state

What does the get_world_state tool do? +

Retrieves the current state of the generated world. 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 get_world_state? +

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

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

Can I rate-limit get_world_state? +

Yes. Add a rate_limit block to the get_world_state 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 get_world_state completely? +

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

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

Free to start. No card required.

47 Rpg tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.