record_video · Mac-Camera- MCP: Risk & Policy

WHAT IT DOES

What record_video does on Mac-Camera-MCP

AI agents invoke record_video to trigger actions in Mac-Camera-MCP. 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 record_video needs a policy

Recording video via the system camera is an external operation that activates hardware (camera/microphone), captures potentially sensitive data, and invokes ffmpeg. This goes beyond a simple write — it triggers real-world device operations. The description is minimal (only mentions output directory), but context from the server description makes the function clear.

From the tool's definition Tool name 'record_video' on a server described as enabling 'video recording using the system camera via ffmpeg'; description mentions output directory path for recording.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

record_video Rate-limited

record_video 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": {
    "record_video": {
      "limits": [
        {
          "counter": "record_video_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 Mac-Camera-MCP, so you can run agents against it safely.

FAQ

Questions about record_video

What does the record_video tool do? +

输出目录路径（可选，默认 ./output）. It is categorised as a Execute tool in the Mac-Camera-MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on record_video? +

Register the Mac-Camera- MCP server in PolicyLayer and add a rule for 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 Mac-Camera-MCP. Nothing to install.

What risk level is record_video? +

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

Can I rate-limit record_video? +

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

How do I block record_video completely? +

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

What MCP server provides record_video? +

record_video is provided by the Mac-Camera- MCP server (mcpservice/mac-camera-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.