run_vql
AI agents invoke run_vql 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.
VQL is Velociraptor's query language capable of running arbitrary forensic queries and operations on target systems. Without restrictions, 'run_vql' would allow an AI agent to execute potentially any Velociraptor operation—from file enumeration to process termination to system remediation. The blast radius is high because VQL's effects depend entirely on query arguments.
From the tool's definition Tool name 'run_vql' in context of Velociraptor MCP Server; VQL (Velociraptor Query Language) is an execution-oriented language for forensic analysis.
Attacks that exploit this kind of access
run_vql. 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.
Register the Velociraptor MCP Server MCP server in PolicyLayer and add a rule for run_vql: 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.
run_vql is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the run_vql 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.
Set action: deny in the PolicyLayer policy for run_vql. 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.
run_vql 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →