macos_quarantine_events
AI agents call macos_quarantine_events 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.
Based on the tool name and its alignment with sibling Read-category tools that collect forensic data (client_info, collect_artifact, etc.), this tool most likely retrieves quarantine event records from macOS systems for forensic analysis. This is consistent with Velociraptor's incident response mission.
From the tool's definition Tool name 'macos_quarantine_events' suggests querying/retrieving macOS quarantine event logs. Description is empty, but the naming pattern matches other Read tools on this server (e.g., 'linux_arp_cache', 'linux_bash_history') which retrieve system…
Attacks that exploit this kind of access
macos_quarantine_events. 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_quarantine_events: 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_quarantine_events 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_quarantine_events 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_quarantine_events. 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_quarantine_events 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 →