pilotgentic_window_recording_manager

WHAT IT DOES

What pilotgentic_window_recording_manager does on PilotGentic

AI agents invoke pilotgentic_window_recording_manager 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.

WHY IT NEEDS A POLICY

Why pilotgentic_window_recording_manager needs a policy

This tool triggers and controls screen recording sessions via macOS screencapture, an external OS-level operation. Recording sessions can capture sensitive on-screen data (passwords, private communications, financial info). It falls under Execute because it runs/triggers external OS operations whose effects depend on arguments (start/stop recording, which windows to capture).

From the tool's definition Manages screen/window recording sessions using macOS screencapture

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

pilotgentic_window_recording_manager Rate-limited

pilotgentic_window_recording_manager 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "pilotgentic_window_recording_manager": {
      "limits": [
        {
          "counter": "pilotgentic_window_recording_manager_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches PilotGentic, so you can run agents against it safely.

FAQ

Questions about pilotgentic_window_recording_manager

What does the pilotgentic_window_recording_manager tool do? +

Manages screen/window recording sessions using macOS screencapture. 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.

How do I enforce a policy on pilotgentic_window_recording_manager? +

Register the PilotGentic MCP server in PolicyLayer and add a rule for pilotgentic_window_recording_manager: 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.

What risk level is pilotgentic_window_recording_manager? +

pilotgentic_window_recording_manager is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit pilotgentic_window_recording_manager? +

Yes. Add a rate_limit block to the pilotgentic_window_recording_manager 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.

How do I block pilotgentic_window_recording_manager completely? +

Set action: deny in the PolicyLayer policy for pilotgentic_window_recording_manager. 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.

What MCP server provides pilotgentic_window_recording_manager? +

pilotgentic_window_recording_manager 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.