Low Risk

get_component_preview

Get component preview information including styling and usage

How to control get_component_preview ↓

What get_component_preview does on OriginUI MCP Server

AI agents call get_component_preview to retrieve information from OriginUI MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why get_component_preview needs a policy

This tool retrieves preview data about UI components (styling and usage information). It has no side effects, does not modify any state, does not execute code, and does not interact with external systems beyond reading component metadata. It is purely a read operation with minimal risk of misuse.

From the tool's definition Tool name 'get_component_preview' and description 'Get component preview information including styling and usage' indicate data retrieval only.

Documented attack patterns abuse exactly the kind of access get_component_preview gives an agent:

How to control get_component_preview

PolicyLayer is an MCP gateway — it sits between your AI agents and OriginUI MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_component_preview:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_component_preview": {}
  }
}

get_component_preview is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register OriginUI MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_component_preview

What does the get_component_preview tool do? +

Get component preview information including styling and usage. It is categorised as a Read tool in the OriginUI MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_component_preview? +

Register the OriginUI MCP Server MCP server in PolicyLayer and add a rule for get_component_preview: 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 OriginUI MCP Server. Nothing to install.

What risk level is get_component_preview? +

get_component_preview is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_component_preview? +

Yes. Add a rate_limit block to the get_component_preview 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.

How do I block get_component_preview completely? +

Set action: deny in the PolicyLayer policy for get_component_preview. 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.

What MCP server provides get_component_preview? +

get_component_preview is provided by the OriginUI MCP Server MCP server (kelvinchng/origin-ui-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every OriginUI MCP Server tool call.

Start from OriginUI 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.

7 OriginUI MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.