Create a new Assembly Definition (.asmdef) file for code containerisation and compilation optimisation. Assembly definitions split your project code into separate assemblies, reducing recompilation time and enforcing clean dependency boundaries.
AI agents use unity_asmdef_create to create or update resources in Unity MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Unity MCP Server environment.
The tool creates a new .asmdef file, which is a reversible modification to the project structure. Assembly definition files are standard Unity project configuration files used for code organization and compilation optimization. This is a write operation (not destructive) because the file can be deleted or modified later.
From the tool's definition Tool description states 'Create a new Assembly Definition (.asmdef) file', which is a create operation that adds a new configuration file to the project.
Documented attack patterns abuse exactly the kind of access unity_asmdef_create gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Unity MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for unity_asmdef_create:
{
"version": "1",
"default": "deny",
"tools": {
"unity_asmdef_create": {
"limits": [
{
"counter": "unity_asmdef_create_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}unity_asmdef_create 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.
Create a new Assembly Definition (.asmdef) file for code containerisation and compilation optimisation. Assembly definitions split your project code into separate assemblies, reducing recompilation time and enforcing clean dependency boundaries. It is categorised as a Write tool in the Unity MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Unity MCP Server MCP server in PolicyLayer and add a rule for unity_asmdef_create: 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 Unity MCP Server. Nothing to install.
unity_asmdef_create 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 unity_asmdef_create 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 unity_asmdef_create. 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.
unity_asmdef_create is provided by the Unity MCP Server MCP server (anklebreaker-studio/unity-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 324 Unity MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
324 Unity MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.