Un-soft-delete an asset. Revives its tombstoned COs with
AI agents use restore_asset 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.
While the tool reverts a soft-delete (technically undoing a destructive action), it is classified as Write rather than Destructive because: (1) it is reversible by soft-deleting again, (2) soft-deletes are typically non-destructive metadata changes in security/compliance platforms, and (3) the tool's purpose is data state modification, not irreversible destruction.
From the tool's definition restore_asset undeletes or revives a soft-deleted asset and its associated control objectives (COs). The description states it 'Un-soft-delete an asset' and 'Revives its tombstoned COs,' indicating a reversal of a deletion state.
Attacks that exploit this kind of access
Un-soft-delete an asset. Revives its tombstoned COs with. 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_asset: 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_asset 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_asset 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_asset. 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_asset 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 →