add_actor_binding
Bind an actor to a level sequence for animation.
This record as markdown: /tools/jjpxdev-unreal-mcp/add-actor-binding.md
What add_actor_binding does on Unreal
AI agents use add_actor_binding to create or update resources in Unreal, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Unreal environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
actor_name | string | Yes | Actor name or label to bind |
sequence_path | string | Yes | LevelSequence asset path |
Parameters from the server's own tool schema.
Why add_actor_binding is rated Medium
The tool creates or modifies metadata (actor bindings) in a level sequence, which is a Write operation. The severity is medium because while the change is reversible and confined to animation bindings (not destructive), misuse could corrupt animation sequences or create unintended bindings that require manual cleanup. The blast radius is limited to animation/sequencing systems rather than core gameplay or assets.
From the tool's definition Tool name 'add_actor_binding' and description 'Bind an actor to a level sequence for animation' indicate creating/modifying a binding relationship between an actor and a level sequence.
Attacks that exploit this kind of access
The rule that runs add_actor_binding safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Unreal, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For add_actor_binding, this is the rule to start with:
add_actor_binding 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 Unreal, apply this rule, and every add_actor_binding call is checked against it from then on.
Questions about add_actor_binding
Bind an actor to a level sequence for animation. It is categorised as a Write tool in the Unreal MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
add_actor_binding accepts 2 parameters: actor_name, sequence_path. Required: actor_name, sequence_path. The full parameter table on this page comes from the server's own tool schema.
Register the Unreal MCP server in PolicyLayer and add a rule for add_actor_binding: 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 Unreal. Nothing to install.
add_actor_binding 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 add_actor_binding 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 add_actor_binding. 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.
add_actor_binding is provided by the Unreal MCP server (@jjpxdev/unreal-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Unreal, and thousands of servers like it.
This server
Across the catalogue