recording_start

What recording_start does on Mcp Anything

AI agents invoke recording_start to trigger actions in Mcp Anything. 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 recording_start is rated High

This tool executes a command with side effects—it initiates a recording process that captures external data and creates files or streams. While not destructive (reversible by stopping the recording) and not inherently dangerous, the initiated operation's scope and impact depend on what is being recorded and where output is directed.

From the tool's definition Tool name 'recording_start' indicates initiation of a recording operation. The description 'Start recording' confirms this is an action that triggers an external operation (likely audio/video recording) whose effects depend on system state and configuration…

The rule that runs recording_start safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Anything, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For recording_start, this is the rule to start with:

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

Questions about recording_start