Low Risk

search_design_tokens

KRDS 디자인 토큰을 검색합니다 (색상, 간격, 타이포그래피 등).

Risk signalsAccepts freeform code/query input (query)

Part of the KRDS Design System server.

search_design_tokens is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE KRDS DESIGN SYSTEM →

Free to start. No card required.

AI agents call search_design_tokens to retrieve information from KRDS Design System without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though search_design_tokens only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "search_design_tokens": {}
  }
}

See the full KRDS Design System policy for all 9 tools.

Get this rule live on your own KRDS Design System server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY KRDS DESIGN SYSTEM →

View all 9 tools →

These attack patterns abuse exactly the kind of access search_design_tokens gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so search_design_tokens only ever does what you allow.

SECURE KRDS DESIGN SYSTEM →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the search_design_tokens tool do? +

KRDS 디자인 토큰을 검색합니다 (색상, 간격, 타이포그래피 등).. It is categorised as a Read tool in the KRDS Design System MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on search_design_tokens? +

Register the KRDS Design System MCP server in PolicyLayer and add a rule for search_design_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 KRDS Design System. Nothing to install.

What risk level is search_design_tokens? +

search_design_tokens is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit search_design_tokens? +

Yes. Add a rate_limit block to the search_design_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.

How do I block search_design_tokens completely? +

Set action: deny in the PolicyLayer policy for search_design_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.

What MCP server provides search_design_tokens? +

search_design_tokens is provided by the KRDS Design System MCP server (re-rank/uiux-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every KRDS Design System tool call.

Deterministic rules across all 9 KRDS Design System tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.