AI agents call list_guidelines 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 retrieves and queries design system documentation without any side effects. It is purely informational—listing guidelines does not create, modify, delete, or execute anything. The tool falls clearly into the Read category with low severity since misuse would only result in viewing design documentation.
From the tool's definition Tool name 'list_guidelines' and description indicating it 'returns a list of Levit design system guidelines' for finding documentation on accessibility, color usage, and component principles.
Attacks that exploit this kind of access
Levit 디자인 시스템 가이드라인 목록을 반환합니다. 접근성, 컬러 사용, 컴포넌트 원칙 같은 문서를 찾을 때 사용하세요. 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_guidelines: 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_guidelines 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_guidelines 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_guidelines. 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_guidelines 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 →