# recording_set_output

A write tool on the Mcp Anything MCP server.

Agent View of the PolicyLayer registry record for `recording_set_output`. HTML page: https://policylayer.com/tools/mcp-anything/recording-set-output

## Facts

- Tool: `recording_set_output`
- Server: Mcp Anything (`Zaymadkid/mcp-anything`) — https://policylayer.com/tools/mcp-anything.md
- Homepage: https://github.com/Zaymadkid/mcp-anything
- Risk category: Write (Medium risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Rate-limited

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "recording_set_output",
    "arguments": {}
  }
}
```

## Why recording_set_output is rated Medium

The 'set_*' naming convention across sibling tools suggests reversible configuration changes (Write category). Without description details, confidence is moderate. If this sets recording output path or format, it modifies system state but remains reversible by re-running with different parameters.

From the tool's own definition: "Tool name 'recording_set_output' suggests configuring or modifying recording destination/parameters. Sibling tools like 'animation_set_fps', 'animation_set_frame_range', 'camera_set_active' follow a pattern of state-modification operations."

## Use case

AI agents use recording_set_output to create or update resources in Mcp Anything, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Anything environment.

## Recommended policy (PolicyLayer)

Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Mcp Anything:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "recording_set_output": {
      "limits": [
        {
          "counter": "recording_set_output_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on Mcp Anything (260)

- `cli_uninstall` — Destructive — https://policylayer.com/tools/mcp-anything/cli-uninstall.md
- `component_remove` — Destructive — https://policylayer.com/tools/mcp-anything/component-remove.md
- `cookie_clear` — Destructive — https://policylayer.com/tools/mcp-anything/cookie-clear.md
- `cookie_delete` — Destructive — https://policylayer.com/tools/mcp-anything/cookie-delete.md
- `doc_paragraph_remove` — Destructive — https://policylayer.com/tools/mcp-anything/doc-paragraph-remove.md
- `doc_remove_element` — Destructive — https://policylayer.com/tools/mcp-anything/doc-remove-element.md
- `filter_remove` — Destructive — https://policylayer.com/tools/mcp-anything/filter-remove.md
- `layer_remove` — Destructive — https://policylayer.com/tools/mcp-anything/layer-remove.md
- `network_clear_log` — Destructive — https://policylayer.com/tools/mcp-anything/network-clear-log.md
- `network_remove_interceptor` — Destructive — https://policylayer.com/tools/mcp-anything/network-remove-interceptor.md
- `node_remove` — Destructive — https://policylayer.com/tools/mcp-anything/node-remove.md
- `object_remove` — Destructive — https://policylayer.com/tools/mcp-anything/object-remove.md
- `pres_slide_remove` — Destructive — https://policylayer.com/tools/mcp-anything/pres-slide-remove.md
- `scene_remove` — Destructive — https://policylayer.com/tools/mcp-anything/scene-remove.md
- `script_remove` — Destructive — https://policylayer.com/tools/mcp-anything/script-remove.md
- `selection_none` — Destructive — https://policylayer.com/tools/mcp-anything/selection-none.md
- `session_reset` — Destructive — https://policylayer.com/tools/mcp-anything/session-reset.md
- `sheet_delete` — Destructive — https://policylayer.com/tools/mcp-anything/sheet-delete.md
- `source_remove` — Destructive — https://policylayer.com/tools/mcp-anything/source-remove.md
- `storage_clear_local` — Destructive — https://policylayer.com/tools/mcp-anything/storage-clear-local.md
- `storage_remove_local` — Destructive — https://policylayer.com/tools/mcp-anything/storage-remove-local.md
- `build_configure` — Execute — https://policylayer.com/tools/mcp-anything/build-configure.md
- `build_run` — Execute — https://policylayer.com/tools/mcp-anything/build-run.md
- `cli_by_category` — Execute — https://policylayer.com/tools/mcp-anything/cli-by-category.md
- `cli_install` — Execute — https://policylayer.com/tools/mcp-anything/cli-install.md
- `cli_run` — Execute — https://policylayer.com/tools/mcp-anything/cli-run.md
- `element_click` — Execute — https://policylayer.com/tools/mcp-anything/element-click.md
- `element_hover` — Execute — https://policylayer.com/tools/mcp-anything/element-hover.md
- `element_scroll_to` — Execute — https://policylayer.com/tools/mcp-anything/element-scroll-to.md
- `form_submit` — Execute — https://policylayer.com/tools/mcp-anything/form-submit.md
- …and 230 more: https://policylayer.com/tools/mcp-anything.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=mcp-anything · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/mcp-anything