AI agents call get_component_usage to retrieve information from GDS MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves and returns design system metadata (component usage rules and specifications). This is a read-only operation with no side effects—it does not modify, delete, execute code, or commit financial transactions. The described purpose is purely informational lookup within the design system.
From the tool's definition Tool returns usage rules and specifications for a design system component ('특정 컴포넌트의 사용 규칙(usage)과 스펙을 반환합니다'). It is a query/retrieval operation similar to sibling tools like get_guideline, get_token, and get_component_code_usage.
Attacks that exploit this kind of access
특정 컴포넌트의 사용 규칙(usage)과 스펙을 반환합니다. 컴포넌트를 언제·어떻게 써야 하는지 확인할 때 사용하세요. It is categorised as a Read tool in the GDS MCP MCP Server, which means it retrieves data without modifying state.
Register the GDS MCP server in PolicyLayer and add a rule for get_component_usage: 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 GDS MCP. Nothing to install.
get_component_usage 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 get_component_usage 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 get_component_usage. 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.
get_component_usage is provided by the GDS MCP server (supin-kim-ilevit-com/gds-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 →