Retrieve client information from the Velociraptor server.
AI agents call client_info 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 retrieves or queries client metadata from Velociraptor without creating, modifying, deleting, or executing any operations. It is a passive information-gathering function typical of forensic data collection interfaces. The blast radius of misuse is minimal—an agent could enumerate clients but cannot trigger remediation, execute commands, or delete data.
From the tool's definition Tool name 'client_info' and description 'Retrieve client information from the Velociraptor server' indicate a data retrieval operation with no modification or execution of external commands.
Attacks that exploit this kind of access
Retrieve client information from the Velociraptor server. 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 client_info: 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.
client_info 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 client_info 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 client_info. 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.
client_info 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 →