Archive old resolved discussions and optionally delete old archived ones. Use for maintenance.
AI agents call discussion_cleanup to permanently remove resources in Lockstep — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Although the primary action (archiving) is reversible, the tool explicitly permits deletion of archived discussions, which is irreversible and cannot be undone. When a tool spans multiple categories (Write for archiving, Destructive for deletion), the most severe applies.
From the tool's definition Tool description states it can 'optionally delete old archived ones' and is used for 'maintenance.' The word 'delete' indicates irreversible removal of discussion data.
Attacks that exploit this kind of access
Archive old resolved discussions and optionally delete old archived ones. Use for maintenance. It is categorised as a Destructive tool in the Lockstep MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Lockstep MCP server in PolicyLayer and add a rule for discussion_cleanup: 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 Lockstep. Nothing to install.
discussion_cleanup is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the discussion_cleanup 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 discussion_cleanup. 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.
discussion_cleanup is provided by the Lockstep MCP server (tmmoore286/lockstep-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 →