macos_bash_history
AI agents call macos_bash_history 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 historical bash commands executed on macOS systems. Bash history is a read-only forensic artifact that reveals past user activity but does not modify, execute, or delete data. It poses minimal risk even if misused by an AI agent, as the worst outcome would be information disclosure of past commands.
From the tool's definition Tool name 'macos_bash_history' indicates retrieval of bash command history from macOS systems. The sibling tools include similar read operations like 'linux_bash_history', 'linux_arp_cache', 'client_info', and 'collect_artifact', all of which are forensic…
Attacks that exploit this kind of access
macos_bash_history. 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 macos_bash_history: 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.
macos_bash_history 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 macos_bash_history 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 macos_bash_history. 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.
macos_bash_history 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 →