Low Risk

statecli_undo

Undo state changes. Rollback when something went wrong. Use when you made a mistake, need to retry, or want to revert.

Part of the Statecli server.

statecli_undo is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE STATECLI →

Free to start. No card required.

AI agents call statecli_undo to retrieve information from Statecli without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though statecli_undo only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "statecli_undo": {}
  }
}

See the full Statecli policy for all 5 tools.

Get this rule live on your own Statecli server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY STATECLI →

These attack patterns abuse exactly the kind of access statecli_undo gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so statecli_undo only ever does what you allow.

SECURE STATECLI →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the statecli_undo tool do? +

Undo state changes. Rollback when something went wrong. Use when you made a mistake, need to retry, or want to revert.. It is categorised as a Read tool in the Statecli MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on statecli_undo? +

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

What risk level is statecli_undo? +

statecli_undo is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit statecli_undo? +

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

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

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

Enforce policy on every Statecli tool call.

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

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.