AI agents call list_tokens 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.
This tool performs a straightforward data retrieval operation against a design system metadata store. It lists or enumerates design tokens in various categories without creating, modifying, deleting, executing code, or moving money. This is a pure Read operation with minimal risk—misuse would only retrieve design metadata already intended to be queryable.
From the tool's definition Tool name 'list_tokens' and description indicate it 'retrieves/queries tokens by category' from the design system (color, spacing, typography, effect).
Attacks that exploit this kind of access
Levit 디자인 시스템의 토큰을 카테고리별로 조회합니다. color, spacing, typography, effect 등 전체 토큰을 탐색할 때 사용하세요. 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 list_tokens: 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.
list_tokens 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_tokens 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_tokens. 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_tokens 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 →