redo · Filopastry MCP: Risk & Policy

WHAT IT DOES

What redo does on Filopastry

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

WHY IT NEEDS A POLICY

Why redo needs a policy

A redo operation re-applies a previously undone change, which is a write/modify action. In the context of a music live-coding environment, this would restore a previously undone pattern or composition change. It is reversible (can be undone again), so it falls under Write rather than Destructive. Severity is low as the blast radius is limited to the local music composition state.

From the tool's definition 'Redo action' - implies re-applying a previously undone operation within the music composition environment

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

redo Rate-limited

redo stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "redo": {
      "limits": [
        {
          "counter": "redo_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Filopastry, so you can run agents against it safely.

FAQ

Questions about redo

What does the redo tool do? +

Redo action. It is categorised as a Write tool in the Filopastry MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on redo? +

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

What risk level is redo? +

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

Can I rate-limit redo? +

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

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

redo is provided by the Filopastry MCP server (youwenshao/filopastry). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.