this will give you the list of all components that are avaialble in the design system
AI agents call get_avaialble_components to retrieve information from Zendesign MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and lists available design system components. It performs no side effects, modifications, deletions, code execution, or financial operations. It is a straightforward read-only query operation with minimal risk even if misused by an AI agent.
From the tool's definition Tool name 'get_avaialble_components' and description 'this will give you the list of all components that are avaialble in the design system' indicate a retrieval/query operation that returns a list without modifying any data.
Attacks that exploit this kind of access
this will give you the list of all components that are avaialble in the design system. It is categorised as a Read tool in the Zendesign MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Zendesign MCP Server MCP server in PolicyLayer and add a rule for get_avaialble_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 Zendesign MCP Server. Nothing to install.
get_avaialble_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_avaialble_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_avaialble_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_avaialble_components is provided by the Zendesign MCP Server MCP server (vishnumallela/zendesign-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 →