AI agents call get_operation to retrieve information from Worldlabs without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Despite the empty description reducing confidence slightly, the 'get_' prefix strongly indicates a read operation that queries operation status or details. In the context of a World Labs generation service, this likely retrieves metadata about async operations (e.g., generation progress).
From the tool's definition Tool name 'get_operation' indicates a retrieval/query function. Description is empty, but naming convention and sibling tools (generate_world_*, list_worlds, get_world, delete_world, broadcast_*) suggest this follows a standard CRUD pattern where 'get_'…
Documented attack patterns abuse exactly the kind of access get_operation gives an agent:
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_operation:
{
"version": "1",
"default": "deny",
"tools": {
"get_operation": {}
}
}get_operation is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
get_operation. It is categorised as a Read tool in the Worldlabs MCP Server, which means it retrieves data without modifying state.
Register the Worldlabs MCP server in PolicyLayer and add a rule for get_operation: 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.
get_operation is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_operation 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 get_operation. 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.
get_operation 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.
Start from Worldlabs, 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.
20 Worldlabs tools catalogued and risk-classified — across an index of 43,000+ MCP servers.