get_install_command

THE RISK

Low Risk

Why get_install_command needs a policy

This tool retrieves and returns installation command metadata for a OriginUI component. It does not execute commands, modify system state, or alter data. It is purely informational, similar to 'get_component_details' and 'get_component_preview' on the same server. The actual execution of the command remains under user control.

From the tool's definition Tool name 'get_install_command' and description 'Get the installation command for a specific component' indicate retrieval of command information.

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

POLICY

How to control get_install_command

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

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_install_command": {}
  }
}

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

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

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More OriginUI MCP Server tools

Read get_component_details Get detailed information about a specific OriginUI component Read get_component_preview Get component preview information including styling and usage Read get_component_screenshot Get component screenshot/visual preview to help assess if it fits the project Read get_registry_stats Get comprehensive statistics about the OriginUI component registry Read list_components List all available OriginUI components with basic information Read search_components Search OriginUI components by name, category, or tags

All 7 OriginUI MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get_install_command

What does the get_install_command tool do? +

Get the installation command for a specific component. 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_install_command? +

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

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

Can I rate-limit get_install_command? +

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

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

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

CHECK YOUR STACK →