AI agents call get_components 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 queries and returns information about available components in the Ameba Design System Spindle. It performs a read-only retrieval operation similar to sibling tools like get_component_info, get_icons, and get_design_tokens. There is no modification, deletion, or execution of external operations involved.
From the tool's definition Tool name 'get_components' and description '利用可能なコンポーネントの一覧を取得します' (retrieves a list of available components) indicate a retrieval operation with no 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_components: 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_components 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_components 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_components. 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_components 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.