run_plugin

THE RISK

High Risk

Why run_plugin needs a policy

This tool permits execution of Volatility3 plugins with user-supplied arguments, making it an Execute-category tool. While the intended use is memory forensics analysis (legitimate), the blast radius is high because: (1) a compromised agent could invoke plugins to exfiltrate sensitive data from memory dumps, (2) certain plugins could be chained to perform reconnaissance or lateral movement in a forensic context, and…

From the tool's definition Tool name 'run_plugin' combined with description 'Run a Volatility3 plugin with optional arguments' indicates execution of arbitrary code.

Documented attack patterns abuse exactly the kind of access run_plugin gives an agent:

POLICY

How to control run_plugin

PolicyLayer is an MCP gateway — it sits between your AI agents and Volatility3 MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for run_plugin:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "run_plugin": {
      "limits": [
        {
          "counter": "run_plugin_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

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

Create a free account and register Volatility3 MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Volatility3 MCP Server tools

Execute scan_with_yara Scan memory with YARA rules to detect malware signatures. Read initialize_memory_file Initialize the Volatility3 wrapper with a memory dump file. Read detect_os Detect the operating system type from the memory dump. Read get_network_connections Get network connections from the memory dump. Read get_plugin_info Get detailed information about a specific plugin. Read get_processes Get a list of processes from the memory dump. Read list_plugins List all available Volatility3 plugins. Read list_process_open_handles List all open handles for a specific process.

All 9 Volatility3 MCP Server tools →

Execute tools on other servers

Android Forensics ADB MCP Server adb_shell_command EMBA-MCP run_emba_scan Frida Game Hacking MCP remove_breakpoint Procmon request_elevation

Go deeper

High-risk tools in Volatility3 MCP Server → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Agent sandbox → Bounding what an agent can execute and where the boundary should sit.
Least privilege for MCP → Granting agents the minimum tool surface the task needs.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about run_plugin

What does the run_plugin tool do? +

Run a Volatility3 plugin with optional arguments. It is categorised as a Execute tool in the Volatility3 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 run_plugin? +

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

What risk level is run_plugin? +

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

Can I rate-limit run_plugin? +

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

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

run_plugin is provided by the Volatility3 MCP Server MCP server (kirandawadi/volatility3-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Volatility3 MCP Server tool call.

Start from Volatility3 MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →