returns the content code of the component.this includes the component code, the component css, and the component js
AI agents call get_component_code 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 reads existing design system component code without any side effects. It performs a straightforward data retrieval operation similar to 'get' or 'fetch' operations. No data is created, modified, deleted, or executed. The blast radius of misuse is minimal—an AI agent retrieving component code cannot cause harm beyond accessing potentially sensitive design implementation details.
From the tool's definition Tool 'get_component_code' returns component code, CSS, and JS content. Description indicates retrieval only: 'returns the content code' with no modification, deletion, or execution capabilities mentioned.
Attacks that exploit this kind of access
returns the content code of the component.this includes the component code, the component css, and the component js. 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_component_code: 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_component_code 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_code 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_code. 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_code 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 →