Edit properties of an existing O3DE project.
AI agents use edit_project_properties 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.
This tool modifies project properties reversibly without deleting data or executing arbitrary code. It changes configuration but not the project structure irreversibly. Severity is medium because misconfigured project properties could cause build failures or runtime issues, but changes are typically reversible through re-editing.
From the tool's definition Tool name 'edit_project_properties' and description 'Edit properties of an existing O3DE project' indicate modification of project configuration data.
Documented attack patterns abuse exactly the kind of access edit_project_properties 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 edit_project_properties:
{
"version": "1",
"default": "deny",
"tools": {
"edit_project_properties": {
"limits": [
{
"counter": "edit_project_properties_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}edit_project_properties 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.
Edit properties of an existing O3DE project. 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 edit_project_properties: 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.
edit_project_properties 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 edit_project_properties 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 edit_project_properties. 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.
edit_project_properties 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.