world_state_export
Export full world state (all actors with properties) as JSON for AI analysis.
This record as markdown: /tools/quangdang46-uefn-verse-mcp/world-state-export.md
What world_state_export does on Uefn
AI agents call world_state_export to retrieve information from Uefn without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why world_state_export is rated Low
This tool retrieves and exports data (world state) without modifying it. It reads all actors and their properties and serializes them to JSON. The medium severity reflects that it exports potentially large amounts of world data which could expose sensitive project details, but it has no write or destructive side effects.
From the tool's definition Export full world state (all actors with properties) as JSON for AI analysis
Attacks that exploit this kind of access
The rule that runs world_state_export safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Uefn, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For world_state_export, this is the rule to start with:
world_state_export is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Uefn, apply this rule, and every world_state_export call is checked against it from then on.
Questions about world_state_export
Export full world state (all actors with properties) as JSON for AI analysis. It is categorised as a Read tool in the Uefn MCP Server, which means it retrieves data without modifying state.
Register the Uefn MCP server in PolicyLayer and add a rule for world_state_export: 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 Uefn. Nothing to install.
world_state_export 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 world_state_export 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 world_state_export. 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.
world_state_export is provided by the Uefn MCP server (quangdang46/uefn-verse-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Uefn, and thousands of servers like it.
This server
Across the catalogue