Un-soft-delete an attacker. Revives tombstoned COs; un-orphans
AI agents use restore_attacker 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.
This tool reverses a soft-delete operation (restores deleted data), which is a Write action that modifies existing records reversibly. While it restores rather than creates new data, it is recoverable and does not permanently erase information. It does not execute arbitrary code, move money, or permanently destroy data, so it falls short of Execute, Financial, or Destructive categories.
From the tool's definition restore_attacker: 'Un-soft-delete an attacker. Revives tombstoned COs; un-orphans'
Attacks that exploit this kind of access
Un-soft-delete an attacker. Revives tombstoned COs; un-orphans. 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.
Register the Mipiti MCP Server MCP server in PolicyLayer and add a rule for restore_attacker: 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.
restore_attacker is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the restore_attacker 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.
Set action: deny in the PolicyLayer policy for restore_attacker. 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.
restore_attacker 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →