install_and_load_mcp_server · MCP Proxy MCP: Risk & Policy

WHAT IT DOES

What install_and_load_mcp_server does on MCP Proxy

AI agents invoke install_and_load_mcp_server 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_and_load_mcp_server needs a policy

The tool name strongly implies it installs software and loads/activates an MCP server at runtime. Installing and loading external servers is an Execute-level action with high blast radius — it could introduce arbitrary code into the environment. The description is empty, so confidence is reduced, but sibling tools like 'install_mcp_server_from_git' and 'call_dynamic_server_tool' corroborate this interpretation.

From the tool's definition Tool name: 'install_and_load_mcp_server'; server description mentions 'dynamic loading, hot-reloading, and orchestration of MCP servers' and 'programmatic tool calling and workflow automation'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

install_and_load_mcp_server Rate-limited

install_and_load_mcp_server 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_and_load_mcp_server": {
      "limits": [
        {
          "counter": "install_and_load_mcp_server_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_and_load_mcp_server

What does the install_and_load_mcp_server tool do? +

install_and_load_mcp_server. 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_and_load_mcp_server? +

Register the MCP Proxy MCP server in PolicyLayer and add a rule for install_and_load_mcp_server: 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_and_load_mcp_server? +

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

Can I rate-limit install_and_load_mcp_server? +

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

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

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