프로젝트에 특정 팩을 고정/차단한다.
AI agents use set_project_pin 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.
This tool modifies project state by pinning or blocking asset packs, which is a configuration change. It is not destructive (the change is reversible), does not execute arbitrary code or delete data, and affects only metadata/settings. The severity is medium because misuse could prevent access to legitimate assets or lock unwanted packs, impacting workflow but not causing permanent data loss.
From the tool's definition Tool name 'set_project_pin' and description '프로젝트에 특정 팩을 고정/차단한다' (Sets/pins/blocks specific packs in a project) indicates modifying project configuration settings. The action is reversible (pins can be unpinned).
Attacks that exploit this kind of access
프로젝트에 특정 팩을 고정/차단한다. 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 set_project_pin: 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.
set_project_pin 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_project_pin 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_project_pin. 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_project_pin 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 →