161 tools. 118 can modify or destroy data without limits.
22 destructive tools with no built-in limits. Policy required.
Last updated:
Destructive tools (audio_sound_clear_saved, audio_sound_remove_saved, bookmark_remove) permanently delete resources. There is no undo. An agent calling these in a retry loop causes irreversible damage.
Write operations (audio_set_element_volume, audio_sound_add_to_timeline, audio_sound_save) modify state. Without rate limits, an agent can make hundreds of changes in seconds — faster than any human can review or revert.
Execute tools (playback_play, playback_stop) trigger processes with side effects. Builds, notifications, workflows — all fired without throttling.
audio_sound_clear_saved:
rules:
- action: deny Destructive tools should never be available to autonomous agents without human approval.
audio_set_element_volume:
rules:
- rate_limit: 30/hour Prevents bulk unintended modifications from agents caught in loops.
api_health_check:
rules:
- rate_limit: 60/minute Controls API costs and prevents retry loops from exhausting upstream rate limits.
Yes. The Opencut Controller server exposes 22 destructive tools including audio_sound_clear_saved, audio_sound_remove_saved, bookmark_remove. These permanently remove resources with no undo. Intercept blocks destructive tools by default so they never reach the upstream server.
The Opencut Controller server has 94 write tools including audio_set_element_volume, audio_sound_add_to_timeline, audio_sound_save. Set rate limits in your policy file -- for example, rate_limit: 10/hour prevents an agent from making more than 10 modifications per hour. Intercept enforces this at the transport layer.
161 tools across 4 categories: Destructive, Execute, Read, Write. 43 are read-only. 118 can modify, create, or delete data.
One line change. Instead of running the Opencut Controller server directly, prefix it with Intercept: intercept -c io-github-jxue0-opencut-controller.yaml -- npx -y @opencut-controller. Download a pre-built policy from policylayer.com/policies/io-github-jxue0-opencut-controller and adjust the limits to match your use case.
Starter policies available for each. Same risk classification, same one-command setup.
Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.