get_world

THE RISK

Low Risk

Why get_world needs a policy

This tool queries and returns data about an existing world without creating, modifying, deleting, or executing any operations. It is a straightforward read operation with minimal risk.

From the tool's definition Tool name is 'get_world' and description states 'Fetch the latest details for a generated world by its ID' — this is a retrieval operation with no modification or side effects.

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

POLICY

How to control get_world

PolicyLayer is an MCP gateway — it sits between your AI agents and Worldlabs, and nothing reaches the server without passing your rules. This is the rule we recommend for get_world:

policy.json

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

get_world 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 Worldlabs — 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 Worldlabs tools

Destructive delete_world delete_world Execute wait_for_world wait_for_world Execute broadcast_spatial_audio Broadcast spatial audio (Music/Ambience) to the scene. Execute generate_world_from_image generate_world_from_image Execute generate_world_from_media_asset generate_world_from_media_asset Execute generate_world_from_multi_image generate_world_from_multi_image Execute generate_world_from_text generate_world_from_text Execute generate_world_from_video generate_world_from_video

All 20 Worldlabs 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 get_world

What does the get_world tool do? +

Fetch the latest details for a generated world by its ID. It is categorised as a Read tool in the Worldlabs MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_world? +

Register the Worldlabs MCP server in PolicyLayer and add a rule for get_world: 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 Worldlabs. Nothing to install.

What risk level is get_world? +

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

Can I rate-limit get_world? +

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

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

get_world is provided by the Worldlabs MCP server (sandraschi/worldlabs-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Worldlabs tool call.

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

CHECK YOUR STACK →