restore_assumption · Mipiti MCP Server MCP: Risk & Policy

WHAT IT DOES

What restore_assumption does on Mipiti MCP Server

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

WHY IT NEEDS A POLICY

Why restore_assumption needs a policy

The tool modifies security posture data by restoring (reverting) an assumption to a prior state. This is a Write operation—reversible data modification within the Mipiti threat modeling platform. Severity is medium because misuse could corrupt threat model assumptions, affecting security analysis, but the operation itself is reversible via other write tools.

From the tool's definition Tool name 'restore_assumption' and server context showing assumption management (add_assumption, add_assumption via sibling tools). 'Restore' suggests reverting an assumption to a previous state, which is a modifiable operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

restore_assumption Rate-limited

restore_assumption 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": {
    "restore_assumption": {
      "limits": [
        {
          "counter": "restore_assumption_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 Mipiti MCP Server, so you can run agents against it safely.

FAQ

Questions about restore_assumption

What does the restore_assumption tool do? +

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

How do I enforce a policy on restore_assumption? +

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

What risk level is restore_assumption? +

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

Can I rate-limit restore_assumption? +

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

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

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