Unity Asset Store 캐시 디렉터리를 스캔해 .unitypackage 목록을 DB 에 동기화한다.
AI agents use scan_unity_asset_store_cache to create or update resources in Assetcache — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Assetcache environment.
The tool reads the Unity Asset Store cache directory but its primary effect is writing/updating records in a database (synchronization). This is a reversible write operation with medium severity since it modifies DB state but does not delete data or execute arbitrary code.
From the tool's definition '스캔해 .unitypackage 목록을 DB 에 동기화한다' — scans cache directory and synchronizes (writes/updates) the list of .unitypackage files into the database
Attacks that exploit this kind of access
Unity Asset Store 캐시 디렉터리를 스캔해 .unitypackage 목록을 DB 에 동기화한다. It is categorised as a Write tool in the Assetcache MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Assetcache MCP server in PolicyLayer and add a rule for scan_unity_asset_store_cache: 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 Assetcache. Nothing to install.
scan_unity_asset_store_cache 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 scan_unity_asset_store_cache 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 scan_unity_asset_store_cache. 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.
scan_unity_asset_store_cache is provided by the Assetcache MCP server (v0o0v/assetcache-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →