AI agents use set_object_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.
Based on the name alone, 'set_object_property' most likely writes/modifies a property value on a 3D object or actor in Unreal Engine. This is a Write operation. Severity is high because modifying object properties in a scene could have broad unintended effects on scene state, but it is generally reversible. Confidence is reduced due to the empty description.
From the tool's definition Tool name 'set_object_property' implies modifying a property on an object; description is empty and uninformative.
Documented attack patterns abuse exactly the kind of access set_object_property gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Unreal, and nothing reaches the server without passing your rules. This is the rule we recommend for set_object_property:
{
"version": "1",
"default": "deny",
"tools": {
"set_object_property": {
"limits": [
{
"counter": "set_object_property_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} set_object_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.
Free to start. No card required.
set_object_property. 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_object_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_object_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_object_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_object_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_object_property is provided by the Unreal MCP server (runeape-sats/unreal-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 21 Unreal tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
21 Unreal tools catalogued and risk-classified — across an index of 42,500+ MCP servers.