Medium Risk

history_can_undo

Check if undo is available

Part of the Opencut Controller MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents use history_can_undo to create or modify resources in Opencut Controller. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

Without a policy, an AI agent could call history_can_undo repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Opencut Controller.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

io-github-jxue0-opencut-controller.yaml
tools:
  history_can_undo:
    rules:
      - action: allow
        rate_limit:
          max: 30
          window: 60

See the full Opencut Controller policy for all 161 tools.

Tool Name history_can_undo
Category Write
Risk Level Medium

View all 161 tools →

Agents calling write-class tools like history_can_undo have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

What does the history_can_undo tool do? +

Check if undo is available. It is categorised as a Write tool in the Opencut Controller MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on history_can_undo? +

Add a rule in your Intercept YAML policy under the tools section for history_can_undo. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Opencut Controller MCP server.

What risk level is history_can_undo? +

history_can_undo is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit history_can_undo? +

Yes. Add a rate_limit block to the history_can_undo rule in your Intercept 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 history_can_undo completely? +

Set action: deny in the Intercept policy for history_can_undo. 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 history_can_undo? +

history_can_undo is provided by the Opencut Controller MCP server (opencut-controller). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Let agents act without letting them run wild.

Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.

Currently onboarding teams running MCP in production.
// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.

// REQUEST EARLY ACCESS

We're letting people in as fast as we can.

You're in the queue.

We'll be in touch as soon as we can let you in.