record_screen
Record the screen for a specified duration (1-60 seconds). Returns the recording as a .mov file path. Requires Screen Recording permission.
This record as markdown: /tools/io-github-heznpc-iconnect/record-screen.md
What record_screen does on Iconnect
AI agents invoke record_screen to trigger actions in Iconnect. 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.
Why record_screen is rated High
This tool captures screen content and writes it to a file, triggering an external OS-level recording operation. It involves executing a screen capture process that records potentially sensitive on-screen information (passwords, private data, confidential documents). The blast radius is high because a misused agent could silently record user activity and save it to disk.
From the tool's definition Record the screen for a specified duration... Returns the recording as a .mov file path. Requires Screen Recording permission.
Attacks that exploit this kind of access
The rule that runs record_screen safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Iconnect, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For record_screen, this is the rule to start with:
record_screen stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Iconnect, apply this rule, and every record_screen call is checked against it from then on.
Questions about record_screen
Record the screen for a specified duration (1-60 seconds). Returns the recording as a .mov file path. Requires Screen Recording permission. It is categorised as a Execute tool in the Iconnect MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Iconnect MCP server in PolicyLayer and add a rule for record_screen: 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 Iconnect. Nothing to install.
record_screen 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 record_screen 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 record_screen. 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.
record_screen is provided by the Iconnect MCP server (iconnect-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Iconnect, and thousands of servers like it.
Across the catalogue