AI agents invoke simctl_record_video to trigger actions in Simctl. 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.
Based on the tool name and server context (xcrun simctl commands for iOS Simulator management), this tool likely initiates a video recording of the simulator screen. This is an Execute-category action as it triggers an external operation (recording) whose effects depend on arguments. The description is empty, lowering confidence.
From the tool's definition Tool name 'simctl_record_video' suggests it triggers a video recording operation on an iOS Simulator via xcrun simctl; description is empty and uninformative.
Attacks that exploit this kind of access
simctl_record_video. It is categorised as a Execute tool in the Simctl MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Simctl MCP server in PolicyLayer and add a rule for simctl_record_video: 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 Simctl. Nothing to install.
simctl_record_video 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 simctl_record_video 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 simctl_record_video. 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.
simctl_record_video is provided by the Simctl MCP server (nzrsky/simctl-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
simctl_record_video is one line of Simctl's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →