AI agents call get_component_info 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 is a retrieval/query operation on a design system component library. It fetches read-only information about components without side effects, side-by-side with similar tools like get_components, get_icon_info, and get_icons which are all standard Read operations. No data modification or code execution occurs.
From the tool's definition Tool name 'get_component_info' and description indicating retrieval of 'detailed information' (詳細情報を取得します means 'retrieves detailed information') for a specified component. No modification, deletion, or execution indicated.
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_component_info: 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_component_info 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_component_info 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_component_info. 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_component_info 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.