worldlabs_help

THE RISK

Low Risk

Why worldlabs_help needs a policy

The name suggests a help/documentation lookup tool, which would be a Read operation at most. However, the description is empty, providing no confirmation of what the tool actually does. Given the name pattern and context (a help tool in an MCP server), it is most likely informational/read-only, but the lack of description significantly lowers confidence.

From the tool's definition Tool name is 'worldlabs_help' with an empty description. No functional details are available.

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

POLICY

How to control worldlabs_help

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

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "worldlabs_help": {
      "limits": [
        {
          "counter": "worldlabs_help_rate",
          "window": "minute",
          "max": 60,
          "scope": "grant"
        }
      ]
    }
  }
}

worldlabs_help gets a rate cap, and 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.

SET A RULE FOR 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 →

Other tools on other servers

Android Forensics ADB MCP Server generate_app_analysis_report Ethereum Tools add Math MCP Server complex_analysis_suite Crypto_MCP aes_encrypt

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Tool risk categories → How PolicyLayer classifies MCP tools by what they can do.
MCP tool → What an MCP tool is and how clients discover and call it.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about worldlabs_help

What does the worldlabs_help tool do? +

worldlabs_help. It is categorised as a Other tool in the Worldlabs MCP Server, which means it performs auxiliary operations.

How do I enforce a policy on worldlabs_help? +

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

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

Can I rate-limit worldlabs_help? +

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

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

worldlabs_help 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 →