state_restore · HashPilot MCP: Risk & Policy

WHAT IT DOES

What state_restore does on HashPilot

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

WHY IT NEEDS A POLICY

Why state_restore needs a policy

The tool performs reversible modification of configuration state (address book, network settings) by restoring from a backup file. This qualifies as Write rather than Destructive because the operation is reversible (the previous state can be restored from another backup).

From the tool's definition Tool description explicitly states 'overwrite current address book and network settings' when merge mode is disabled. This is a state modification operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

state_restore Rate-limited

state_restore 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": {
    "state_restore": {
      "limits": [
        {
          "counter": "state_restore_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 HashPilot, so you can run agents against it safely.

FAQ

Questions about state_restore

What does the state_restore tool do? +

Restore MCP server state from a backup file. This will overwrite current address book and network settings unless merge mode is enabled. It is categorised as a Write tool in the HashPilot MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on state_restore? +

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

What risk level is state_restore? +

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

Can I rate-limit state_restore? +

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

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

state_restore is provided by the HashPilot MCP server (justmert/hashpilot). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

state_restore is one line of HashPilot's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →