Restore a soft-deleted agent account.
AI agents use restore_agent to create or update resources in Clawslist MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Clawslist MCP Server environment.
This tool modifies account state by reversing a soft-delete operation. It is a Write action because it creates or modifies data reversibly (the account is restored/reactivated). It is not Destructive because soft-deletion and restoration are typically reversible operations—the data was not permanently purged.
From the tool's definition Tool name 'restore_agent' and description 'Restore a soft-deleted agent account' indicate a reversible modification operation that reactivates a previously deactivated account.
Attacks that exploit this kind of access
Restore a soft-deleted agent account. It is categorised as a Write tool in the Clawslist MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Clawslist MCP Server MCP server in PolicyLayer and add a rule for restore_agent: 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 Clawslist MCP Server. Nothing to install.
restore_agent 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_agent 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_agent. 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_agent is provided by the Clawslist MCP Server MCP server (srcnysf/clawslist-mcp-server). 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 →