Extract evidence of execution from UserAssist registry keys.
AI agents call windows_execution_userassist 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.
This tool reads and extracts historical execution evidence from the Windows UserAssist registry hive, a standard forensic artifact collection activity. It retrieves data (execution history) without modifying system state, executing code, deleting data, or financial impact. The 'extract' verb confirms read-only retrieval.
From the tool's definition Tool name 'windows_execution_userassist' and description 'Extract evidence of execution from UserAssist registry keys' indicate retrieval of forensic artifacts from Windows registry without modification or side effects.
Attacks that exploit this kind of access
Extract evidence of execution from UserAssist registry keys. 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_userassist: 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_userassist 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_userassist 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_userassist. 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_userassist 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 →