High Risk →

replay_diff

replay_diff

How to control replay_diff ↓

AI agents invoke replay_diff to trigger actions in Novyx. 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.

High Risk

The name 'replay_diff' suggests replaying or re-executing some prior action or diff (change), which in the context of a governed MCP server with rollback capabilities likely involves re-applying a recorded state change. This falls closest to Execute given the 'replay' semantics, but confidence is low due to the empty description. In a rollback/audit context it could also be Write or even Destructive.

From the tool's definition Tool name 'replay_diff' — description is empty and uninformative.

Documented attack patterns abuse exactly the kind of access replay_diff gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Novyx, and nothing reaches the server without passing your rules. This is the rule we recommend for replay_diff:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "replay_diff": {
      "limits": [
        {
          "counter": "replay_diff_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

replay_diff stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Novyx — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RATE-LIMIT THIS TOOL →

Free to start. No card required.

Go deeper

What does the replay_diff tool do? +

replay_diff. It is categorised as a Execute tool in the Novyx MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on replay_diff? +

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

What risk level is replay_diff? +

replay_diff is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit replay_diff? +

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

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

replay_diff is provided by the Novyx MCP server (novyxlabs/novyx-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Novyx tool call.

Deterministic rules across all 120 Novyx tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

120 Novyx tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.