windows_powershell_scriptblock · Velociraptor MCP Server MCP

WHAT IT DOES

What windows_powershell_scriptblock does on Velociraptor MCP Server

AI agents invoke windows_powershell_scriptblock to trigger actions in Velociraptor 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 windows_powershell_scriptblock needs a policy

PowerShell scriptblock execution is a high-capability action that can run arbitrary code on remote Windows endpoints. In the context of a digital forensics and incident response platform like Velociraptor, this tool almost certainly executes PowerShell code on client machines. The blast radius is critical — an AI agent could execute destructive, exfiltrating, or backdooring commands across endpoints.

From the tool's definition Tool name 'windows_powershell_scriptblock' strongly implies execution of PowerShell script blocks on Windows systems; description is empty providing no further constraints.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

windows_powershell_scriptblock Rate-limited

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

FAQ

Questions about windows_powershell_scriptblock

What does the windows_powershell_scriptblock tool do? +

windows_powershell_scriptblock. It is categorised as a Execute tool in the Velociraptor 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 windows_powershell_scriptblock? +

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

What risk level is windows_powershell_scriptblock? +

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

Can I rate-limit windows_powershell_scriptblock? +

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

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

windows_powershell_scriptblock is provided by the Velociraptor MCP Server MCP server (snoe-findley/mcp-velociraptor). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.