windows_execution_bam
AI agents call windows_execution_bam to retrieve information from Velociraptor MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
BAM is a Windows forensic artifact that logs application execution history. Given the Velociraptor context (digital forensics/incident response), the tool most likely retrieves or queries historical execution data without side effects. However, confidence is moderate due to the empty description.
From the tool's definition Tool name 'windows_execution_bam' suggests reading Windows BAM (Background Activity Moderator) forensic artifacts, consistent with sibling tools like 'collect_artifact' and 'collect_file' which are Read operations. No description provided to confirm.
Attacks that exploit this kind of access
windows_execution_bam. It is categorised as a Read tool in the Velociraptor MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Velociraptor MCP Server MCP server in PolicyLayer and add a rule for windows_execution_bam: 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.
windows_execution_bam is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the windows_execution_bam 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 windows_execution_bam. 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.
windows_execution_bam 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 →