Medium Risk

actor_lock

Lock actor transforms to prevent accidental movement.

How to control actor_lock ↓

What actor_lock does on Uefn

AI agents use actor_lock 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.

Medium Risk

Why actor_lock needs a policy

This tool modifies actor properties in the UEFN editor by applying a lock constraint. While it prevents further movement, the lock itself can be reversed (via actor_unlock, a sibling tool), making it Write rather than Destructive. Severity is medium because misuse could disrupt editor workflow by locking actors an AI agent shouldn't, but the effect is recoverable.

From the tool's definition Tool description: 'Lock actor transforms to prevent accidental movement.' The tool modifies actor state (applying a transform lock), which is a reversible data change to the editor state.

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

How to control actor_lock

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

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "actor_lock": {
      "limits": [
        {
          "counter": "actor_lock_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

actor_lock 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.

  1. Create a free account and register Uefn — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about actor_lock

What does the actor_lock tool do? +

Lock actor transforms to prevent accidental movement. 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.

How do I enforce a policy on actor_lock? +

Register the Uefn MCP server in PolicyLayer and add a rule for actor_lock: 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.

What risk level is actor_lock? +

actor_lock is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit actor_lock? +

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

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

actor_lock 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.

Enforce policy on every Uefn tool call.

Start from Uefn, 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.

143 Uefn tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.