run_volatility · SIFTGuard MCP: Risk & Policy

WHAT IT DOES

What run_volatility does on SIFTGuard

AI agents invoke run_volatility to trigger actions in SIFTGuard. 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 run_volatility needs a policy

This is Execute rather than Read because it runs code (volatility3 plugins) whose effects and output depend on runtime arguments and the memory dump provided. While volatility is read-only against already-captured memory, the tool triggers external command execution.

From the tool's definition Tool description states 'Run a volatility3 plugin against a memory dump' — this executes external forensic analysis tools (volatility3) with plugin arguments that determine runtime behavior.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_volatility Rate-limited

run_volatility 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": {
    "run_volatility": {
      "limits": [
        {
          "counter": "run_volatility_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 SIFTGuard, so you can run agents against it safely.

FAQ

Questions about run_volatility

What does the run_volatility tool do? +

Run a volatility3 plugin against a memory dump for forensic analysis. Plugins: windows.pslist, windows.netscan, windows.malfind, windows.cmdline. It is categorised as a Execute tool in the SIFTGuard 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_volatility? +

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

What risk level is run_volatility? +

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

Can I rate-limit run_volatility? +

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

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

run_volatility is provided by the SIFTGuard MCP server (sodiq-code/siftguard). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.