AI agents call get_guideline 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 is a straightforward query operation that retrieves design system guideline metadata. It has no side effects—it only reads and returns information from a static design system catalogue. Consistent with sibling tools like get_token, get_component_code_usage, and list_guidelines, all of which are read-only queries.
From the tool's definition Tool name 'get_guideline' and description indicating retrieval of guideline details by ID ('가이드라인 ID로 상세 내용을 조회합니다' = 'Look up detailed guideline content by guideline ID'). No modification, deletion, execution, or financial operations are performed.
Attacks that exploit this kind of access
가이드라인 ID로 상세 내용을 조회합니다. 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_guideline: 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_guideline 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_guideline 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_guideline. 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_guideline 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 →