yara_scan_files
AI agents invoke yara_scan_files 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.
YARA scanning involves executing a scan engine against files on a host system, which triggers external operations on potentially sensitive files. Given the Velociraptor DFIR context (which includes memory scans, remediation actions, and artifact collection), a YARA file scan actively runs pattern-matching code against filesystem targets — this is an Execute-category action.
From the tool's definition Tool name 'yara_scan_files' on a Velociraptor DFIR server; description is empty and uninformative.
Attacks that exploit this kind of access
yara_scan_files. 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 yara_scan_files: 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.
yara_scan_files 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 yara_scan_files 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 yara_scan_files. 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.
yara_scan_files 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 →