reload_plugins · Universal Dev MCP: Risk & Policy

WHAT IT DOES

What reload_plugins does on Universal Dev MCP

AI agents invoke reload_plugins to trigger actions in Universal Dev MCP. 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_plugins needs a policy

The tool dynamically loads plugins/frameworks based on active_plugins configuration during runtime, which constitutes code execution with side effects. While not destructive (reversible via unload), this is Execute-class because it triggers external operations whose effects depend on which plugins are specified.

From the tool's definition Tool description indicates 'load karo' (load/activate) frameworks dynamically without server restart. This is a runtime operation that triggers external code execution and changes application state, similar to plugin/module loading operations.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

reload_plugins Rate-limited

reload_plugins 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_plugins": {
      "limits": [
        {
          "counter": "reload_plugins_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 Universal Dev MCP, so you can run agents against it safely.

FAQ

Questions about reload_plugins

What does the reload_plugins tool do? +

active_plugins config se nayi frameworks load karo bina server restart kiye. It is categorised as a Execute tool in the Universal Dev MCP 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_plugins? +

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

What risk level is reload_plugins? +

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

Can I rate-limit reload_plugins? +

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

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

reload_plugins is provided by the Universal Dev MCP server (kallusuvaidyam/universal_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.