actor_show
Show previously hidden actors in the editor viewport.
This record as markdown: /tools/quangdang46-uefn-verse-mcp/actor-show.md
What actor_show does on Uefn
AI agents use actor_show to create or update resources in Uefn, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Uefn environment.
Why actor_show is rated Medium
This tool reverses a hidden state on actors, making them visible again in the editor. It modifies editor state (visibility) but is reversible (actors can be hidden again). No data is deleted, no code is executed, and no financial operations are involved. It's a Write operation with low severity since it only affects editor viewport visibility.
From the tool's definition Show previously hidden actors in the editor viewport
Attacks that exploit this kind of access
The rule that runs actor_show 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 actor_show, this is the rule to start with:
actor_show stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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 actor_show call is checked against it from then on.
Questions about actor_show
Show previously hidden actors in the editor viewport. It is categorised as a Write tool in the Uefn MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Uefn MCP server in PolicyLayer and add a rule for actor_show: 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.
actor_show is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the actor_show 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 actor_show. 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.
actor_show 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