AI agents use set_playback_range 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.
This tool modifies playback parameters of a sequence in Unreal Engine. While it changes state, the modification is reversible (the playback range can be changed again to different values) and does not create, delete, or irreversibly transform assets. It does not execute arbitrary code or trigger external operations with unpredictable effects—it performs a bounded, well-defined parameter change.
From the tool's definition set_playback_range sets the playback start and end frames of a sequence, which modifies configuration/metadata of a sequence rather than creating new assets or deleting data.
Attacks that exploit this kind of access
Set the playback start and end frames of a sequence. 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.
Register the Unreal MCP server in PolicyLayer and add a rule for set_playback_range: 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.
set_playback_range 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 set_playback_range 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 set_playback_range. 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.
set_playback_range is provided by the Unreal MCP server (sam-david/unreal-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →