install_mcp · MCP Secure Installer MCP: Risk & Policy

WHAT IT DOES

What install_mcp does on MCP Secure Installer

AI agents invoke install_mcp to trigger actions in MCP Secure Installer. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why install_mcp needs a policy

This tool pulls arbitrary code from a GitHub repository and executes it inside a Docker container. An AI agent could be directed to install a malicious repository, resulting in arbitrary code execution within the environment. The blast radius is critical: remote code execution, container escape risks, supply-chain attacks, and potential pivot to host systems are all possible misuses.

From the tool's definition "Install an MCP server from a GitHub repository" — fetches remote code and runs/containerizes it, and the server description states it 'Automatically installs and containerizes MCP servers from GitHub repositories...

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

install_mcp Rate-limited

install_mcp stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "install_mcp": {
      "limits": [
        {
          "counter": "install_mcp_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches MCP Secure Installer, so you can run agents against it safely.

FAQ

Questions about install_mcp

What does the install_mcp tool do? +

Install an MCP server from a GitHub repository. It is categorised as a Execute tool in the MCP Secure Installer MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on install_mcp? +

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

What risk level is install_mcp? +

install_mcp is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit install_mcp? +

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

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

install_mcp is provided by the MCP Secure Installer MCP server (mossaka/mcp-sinstaller). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.