List or play saved MacPilot recordings. Use op:
AI agents invoke pilotgentic_play_recording to trigger actions in PilotGentic. 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.
Playing a recording triggers a sequence of previously captured desktop automation actions (clicks, typing, browser control, etc.), which constitutes executing operations whose effects depend on the recording's contents. The blast radius is high because replaying arbitrary macOS automation could modify files, send messages, or perform other irreversible actions depending on what was recorded.
From the tool's definition 'play saved MacPilot recordings' — playing a recording replays automated actions (clicks, keystrokes, system interactions) on the macOS desktop
Attacks that exploit this kind of access
List or play saved MacPilot recordings. Use op:. It is categorised as a Execute tool in the PilotGentic MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the PilotGentic MCP server in PolicyLayer and add a rule for pilotgentic_play_recording: 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 PilotGentic. Nothing to install.
pilotgentic_play_recording 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 pilotgentic_play_recording 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 pilotgentic_play_recording. 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.
pilotgentic_play_recording is provided by the PilotGentic MCP server (@pilotgentic/mcp-server). 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 →