install_mcp_server_from_git · MCP Proxy MCP: Risk & Policy

WHAT IT DOES

What install_mcp_server_from_git does on MCP Proxy

AI agents invoke install_mcp_server_from_git to trigger actions in MCP Proxy. 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_server_from_git needs a policy

Installing software from a git repository involves cloning remote code and executing installation steps, which constitutes an Execute-level action. The blast radius is high because arbitrary code from a remote source could be installed and run in the environment. Confidence is moderate because the description is empty, so exact behavior is inferred from the name and server context.

From the tool's definition Tool name 'install_mcp_server_from_git' implies fetching code from a git repository and installing/executing it; server description mentions 'dynamic loading' and 'orchestration of MCP servers'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

install_mcp_server_from_git Rate-limited

install_mcp_server_from_git 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_server_from_git": {
      "limits": [
        {
          "counter": "install_mcp_server_from_git_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 Proxy, so you can run agents against it safely.

FAQ

Questions about install_mcp_server_from_git

What does the install_mcp_server_from_git tool do? +

install_mcp_server_from_git. It is categorised as a Execute tool in the MCP Proxy 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_server_from_git? +

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

What risk level is install_mcp_server_from_git? +

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

Can I rate-limit install_mcp_server_from_git? +

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

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

install_mcp_server_from_git is provided by the MCP Proxy MCP server (lizthedeveloper/mcp_proxy). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.