macos_launch_agents
AI agents invoke macos_launch_agents to trigger actions in Velociraptor MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Launch agents on macOS are executable items that run at startup or on-demand. The name 'macos_launch_agents' combined with Velociraptor's remediation action capability indicates this tool can create, modify, or trigger launch agents—triggering external operations whose effects depend on arguments.
From the tool's definition Tool name 'macos_launch_agents' on Velociraptor server for 'remediation actions' and incident response; sibling tools include 'kill_process' and artifact/file collection, indicating capability to interact with system processes and launch configurations.
Attacks that exploit this kind of access
macos_launch_agents. It is categorised as a Execute tool in the Velociraptor MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Velociraptor MCP Server MCP server in PolicyLayer and add a rule for macos_launch_agents: 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_launch_agents is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the macos_launch_agents 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_launch_agents. 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_launch_agents 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 →