AI agents call get_design_tokens to retrieve information from Spindle without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves design tokens from the Ameba Design System Spindle, which is a configuration/metadata query operation. No data is created, modified, deleted, or executed. The tool simply provides access to existing design system definitions, making it a safe Read operation with minimal security risk.
From the tool's definition Tool name 'get_design_tokens' and description 'retrieve defined design tokens' indicate a read-only operation that fetches data without modification or side effects.
Attacks that exploit this kind of access
定義されたデザイントークンを取得します. It is categorised as a Read tool in the Spindle MCP Server, which means it retrieves data without modifying state.
Register the Spindle MCP server in PolicyLayer and add a rule for get_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 Spindle. Nothing to install.
get_design_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 get_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.
Set action: deny in the PolicyLayer policy for get_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.
get_design_tokens is provided by the Spindle MCP server (@openameba/spindle-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.