Low Risk

get_component_screenshot

Get component screenshot/visual preview to help assess if it fits the project

How to control get_component_screenshot ↓

What get_component_screenshot does on OriginUI MCP Server

AI agents call get_component_screenshot 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_screenshot needs a policy

This tool retrieves pre-generated visual previews or screenshots of UI components for inspection purposes. It performs a read-only operation that queries existing data (component assets) without creating, modifying, deleting, or executing any code. The blast radius of misuse is minimal—an AI agent could only retrieve screenshots, not modify the component registry or perform destructive actions.

From the tool's definition Tool name 'get_component_screenshot' and description 'Get component screenshot/visual preview to help assess if it fits the project' indicate retrieval of visual assets with no side effects.

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

How to control get_component_screenshot

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_screenshot:

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

get_component_screenshot 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_screenshot

What does the get_component_screenshot tool do? +

Get component screenshot/visual preview to help assess if it fits the project. 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_screenshot? +

Register the OriginUI MCP Server MCP server in PolicyLayer and add a rule for get_component_screenshot: 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_screenshot? +

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

Can I rate-limit get_component_screenshot? +

Yes. Add a rate_limit block to the get_component_screenshot 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_screenshot completely? +

Set action: deny in the PolicyLayer policy for get_component_screenshot. 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_screenshot? +

get_component_screenshot 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.