자산 채택 이력을 기록한다 (통일성 가중치의 핵심 입력).
AI agents use record_asset_use 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 records asset usage/adoption history, which is a write operation creating new log entries. It feeds into a weighting system ('통일성 가중치의 핵심 입력' = 'key input for consistency weights'), meaning it modifies tracking data. This is reversible data creation/update with low blast radius — misuse would at worst skew recommendation weights.
From the tool's definition '자산 채택 이력을 기록한다' translates to 'Records asset adoption history' — this is a write/logging operation that creates or updates usage history records.
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 record_asset_use: 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.
record_asset_use 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 record_asset_use 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 record_asset_use. 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.
record_asset_use 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 →