set_preset_property
Set a property value exposed via a Remote Control Preset.
This record as markdown: /tools/jjpxdev-unreal-mcp/set-preset-property.md
What set_preset_property does on Unreal
AI agents use set_preset_property 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 |
|---|---|---|---|
value | object | — | Property value to set |
preset_name | string | Yes | Preset name |
property_name | string | Yes | Exposed property name |
Parameters from the server's own tool schema.
Why set_preset_property is rated Medium
This tool modifies properties in Unreal Engine via Remote Control Presets, which are configuration mechanisms that expose engine properties for external manipulation. While the modification is reversible (properties can be set back to previous values), it affects engine state and can have significant consequences depending on which properties are modified - from rendering settings to gameplay logic.
From the tool's definition Tool name and description: 'set_preset_property' - 'Set a property value exposed via a Remote Control Preset.' The verb 'Set' indicates modification of data/properties in Unreal Engine.
Attacks that exploit this kind of access
The rule that runs set_preset_property 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 set_preset_property, this is the rule to start with:
set_preset_property 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 set_preset_property call is checked against it from then on.
Questions about set_preset_property
Set a property value exposed via a Remote Control Preset. 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.
set_preset_property accepts 3 parameters: value, preset_name, property_name. Required: preset_name, property_name. 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 set_preset_property: 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_preset_property 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_preset_property 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_preset_property. 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_preset_property 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