windows_rdp_sessions
AI agents call windows_rdp_sessions 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 appears to query or retrieve information about active or historical RDP sessions on Windows systems for forensic analysis purposes. There is no indication it modifies, executes code, deletes data, or moves money. The primary function is data retrieval.
From the tool's definition Tool name 'windows_rdp_sessions' indicates retrieval of Remote Desktop Protocol session data. No description provided, but the tool belongs to a forensics/incident response server (Velociraptor) alongside other data collection tools like 'collect_artifact',…
Attacks that exploit this kind of access
windows_rdp_sessions. 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_rdp_sessions: 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_rdp_sessions 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_rdp_sessions 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_rdp_sessions. 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_rdp_sessions 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 →