// MCP TOOL REFERENCE

STATECLI TOOLS

5 tools from the Statecli MCP Server, categorised by risk level.

READ TOOLS

statecli_log View state change history for an entity. Use when you need to see past actions, audit trail, or understand behavior. statecli_replay Replay state changes for an entity. Shows step-by-step what happened. Use when debugging, understanding past behavior, or finding errors. statecli_track Explicitly track a state change. Use when making important state modifications. statecli_undo Undo state changes. Rollback when something went wrong. Use when you made a mistake, need to retry, or want to revert.

WRITE TOOLS

statecli_checkpoint Create named checkpoint before making changes. Use when about to do something risky or want a rollback point. 2/5

// FAQ

How many tools does the Statecli MCP server have? +

The Statecli MCP server exposes 5 tools across 2 categories: Read, Write.

How do I enforce policies on Statecli tools? +

Use Intercept, the open-source MCP proxy. Write YAML rules for each tool — rate limits, argument validation, or deny rules — then run Intercept in front of the Statecli server.

What risk categories do Statecli tools fall into? +

Statecli tools are categorised as Read (4), Write (1). Each category has a recommended default policy.

Enforce policies on Statecli

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept

github.com/policylayer/intercept →