Import an external file into the Unity project as an asset.
AI agents use unity_asset_import 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.
This tool creates new asset entries in a Unity project by importing external files. It is a Write operation because it modifies project state by adding assets, which can be subsequently deleted or replaced (reversible). It does not execute arbitrary code, delete data permanently, or move financial resources.
From the tool's definition Tool name 'unity_asset_import' and description 'Import an external file into the Unity project as an asset' indicate the tool adds/ingests new data into a project in a reversible manner.
Documented attack patterns abuse exactly the kind of access unity_asset_import 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_asset_import:
{
"version": "1",
"default": "deny",
"tools": {
"unity_asset_import": {
"limits": [
{
"counter": "unity_asset_import_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}unity_asset_import 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.
Import an external file into the Unity project as an asset. 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_asset_import: 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_asset_import 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_asset_import 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_asset_import. 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_asset_import 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.