Fetches detailed design specifications for a specific Zeplin component, including its properties, variants, layers, and associated design tokens. Use this when you need to understand the structure and styling of a single, reusable UI element from Zeplin.
AI agents call get_component to retrieve information from Zeplin MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves read-only design data from Zeplin. It has no side effects—it does not create, modify, delete, or execute operations. The action is purely informational retrieval of component specifications and styling information needed for UI code generation. Blast radius if misused is minimal; an agent could only access design data it is authorized to view.
From the tool's definition Tool 'fetches' and retrieves 'detailed design specifications' for components, 'properties, variants, layers, and associated design tokens' without modifying or executing anything.
Documented attack patterns abuse exactly the kind of access get_component gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Zeplin MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_component:
{
"version": "1",
"default": "deny",
"tools": {
"get_component": {}
}
}get_component is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Fetches detailed design specifications for a specific Zeplin component, including its properties, variants, layers, and associated design tokens. Use this when you need to understand the structure and styling of a single, reusable UI element from Zeplin. It is categorised as a Read tool in the Zeplin MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Zeplin MCP Server MCP server in PolicyLayer and add a rule for get_component: 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 Zeplin MCP Server. Nothing to install.
get_component 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 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. 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 is provided by the Zeplin MCP Server MCP server (zeplin/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Zeplin MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
4 Zeplin MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.