Collect Shellbags from Registry on a Windows host.
AI agents call windows_shellbags 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.
The tool collects forensic data from a Registry hive without modifying, deleting, or executing code. Registry reads for forensic analysis are Read category operations. Severity is low because shellbags are historical metadata without capability to modify system state, move funds, or trigger destructive actions. This is a standard forensic collection tool used in incident response.
From the tool's definition Tool name 'windows_shellbags' and description 'Collect Shellbags from Registry on a Windows host' indicate a data retrieval operation from the Windows Registry. Shellbags are forensic artifacts containing historical folder access information.
Attacks that exploit this kind of access
Collect Shellbags from Registry on a Windows host. 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_shellbags: 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_shellbags 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_shellbags 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_shellbags. 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_shellbags 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 →