set_component_property
AI agents use set_component_property to create or update resources in O3de — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your O3de environment.
Setting a component property modifies data (the property value) in a reversible manner. This is a Write operation—changes can typically be undone or reverted. Severity is medium because misconfigured properties could break scenes or functionality, but without code execution or data destruction capabilities. Confidence is slightly reduced due to the empty description, which prevents confirmation of exact behavior.
From the tool's definition Tool name 'set_component_property' indicates modification of component properties. Sibling tools include 'add_component', 'create_entity', 'edit_project_properties' which are clearly Write operations.
Documented attack patterns abuse exactly the kind of access set_component_property gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and O3de, and nothing reaches the server without passing your rules. This is the rule we recommend for set_component_property:
{
"version": "1",
"default": "deny",
"tools": {
"set_component_property": {
"limits": [
{
"counter": "set_component_property_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}set_component_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_component_property. It is categorised as a Write tool in the O3de MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the O3de MCP server in PolicyLayer and add a rule for set_component_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 O3de. Nothing to install.
set_component_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_component_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_component_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_component_property is provided by the O3de MCP server (nickschuetz/o3de-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from O3de, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
30 O3de tools catalogued and risk-classified — across an index of 43,000+ MCP servers.