라벨 어휘의 24개 축 목록을 반환한다.
AI agents call list_label_axes to retrieve information from Assetcache without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and enumerates label metadata (the axes/dimensions used in the asset labeling system). It performs a simple read operation on existing data structures without creating, modifying, deleting, or executing any operations. The return of a static list of categorical axes poses minimal risk in isolation.
From the tool's definition Tool name 'list_label_axes' and description indicating it 'returns a list of 24 axes of label vocabulary' — a query operation that retrieves metadata about labeling dimensions with no side effects.
Attacks that exploit this kind of access
라벨 어휘의 24개 축 목록을 반환한다. It is categorised as a Read tool in the Assetcache MCP Server, which means it retrieves data without modifying state.
Register the Assetcache MCP server in PolicyLayer and add a rule for list_label_axes: 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.
list_label_axes is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_label_axes 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 list_label_axes. 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.
list_label_axes 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 →