reload_mcp_server · MCP Proxy MCP: Risk & Policy

WHAT IT DOES

What reload_mcp_server does on MCP Proxy

AI agents invoke reload_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 reload_mcp_server needs a policy

The tool likely triggers a reload/restart of an MCP server process, which is an external operation affecting running services. This falls under Execute as it triggers an external operational action. The description is empty, reducing confidence, but the server context of 'hot-reloading' MCP servers strongly implies this tool restarts or reinitializes a server process.

From the tool's definition Tool name 'reload_mcp_server' combined with server description mentioning 'hot-reloading' and 'orchestration of MCP servers'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

reload_mcp_server Rate-limited

reload_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": {
    "reload_mcp_server": {
      "limits": [
        {
          "counter": "reload_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 reload_mcp_server

What does the reload_mcp_server tool do? +

reload_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 reload_mcp_server? +

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

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

Can I rate-limit reload_mcp_server? +

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

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

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