plugin_exec · Overlord MCP Server MCP: Risk & Policy

WHAT IT DOES

What plugin_exec does on Overlord MCP Server

AI agents invoke plugin_exec to trigger actions in Overlord MCP Server. 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 plugin_exec needs a policy

This tool executes binary code on the Overlord C2 server infrastructure. Given that Overlord is a command-and-control framework, executing arbitrary binaries represents a critical risk: (1) it can run any compiled code with the server's privileges, (2) the effects are dependent on the binary's behavior and arguments, (3) it has potential for lateral movement, data exfiltration, or system compromise, and (4) it…

From the tool's definition Tool name 'plugin_exec' and description 'Execute a binary from a plugin on the Overlord server' indicate execution of arbitrary binaries on the server.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

plugin_exec Rate-limited

plugin_exec 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": {
    "plugin_exec": {
      "limits": [
        {
          "counter": "plugin_exec_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 Overlord MCP Server, so you can run agents against it safely.

FAQ

Questions about plugin_exec

What does the plugin_exec tool do? +

Execute a binary from a plugin on the Overlord server. It is categorised as a Execute tool in the Overlord MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on plugin_exec? +

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

What risk level is plugin_exec? +

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

Can I rate-limit plugin_exec? +

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

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

plugin_exec is provided by the Overlord MCP Server MCP server (skeeminator/overlord-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.