list_clients
AI agents call list_clients 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 performs a read-only operation that retrieves metadata about managed clients. While the description is absent (reducing confidence slightly), the name unambiguously indicates enumeration rather than creation, modification, or deletion. The blast radius of misuse is low—an attacker gaining access could enumerate the fleet topology but cannot damage systems or exfiltrate sensitive data through this tool alone.
From the tool's definition Tool name 'list_clients' indicates a query/retrieval operation. The description is empty, but contextual analysis of the Velociraptor MCP Server (a forensics and incident response platform) combined with the sibling tools (client_info, collect_artifact, etc.)…
Attacks that exploit this kind of access
list_clients. 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 list_clients: 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.
list_clients 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 list_clients 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 list_clients. 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.
list_clients 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 →