AI agents use set_streaming_source 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 actor component properties related to World Partition streaming configuration. While it changes engine state, it does not execute arbitrary code, delete data irreversibly, or trigger financial transactions. The modification is reversible (configuration can be reconfigured), placing it in the Write category.
From the tool's definition Tool name 'set_streaming_source' and description 'Configure a streaming source component on an actor for World Partition' indicate modification of actor component configuration. The verb 'set' and 'configure' denote state changes to game world objects.
Attacks that exploit this kind of access
Configure a streaming source component on an actor for World Partition. 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_streaming_source: 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_streaming_source 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_streaming_source 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_streaming_source. 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_streaming_source 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 →