Deletes a progress entry by its ID.
AI agents call delete_progress_by_id to permanently remove resources in SDOF Knowledge Base — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes data without the ability to undo the operation. While the blast radius is somewhat limited to progress entries within a knowledge base (not affecting core system integrity or external systems), the irreversible nature of deletion places it in the Destructive category.
From the tool's definition Tool name explicitly contains 'delete' and description states 'Deletes a progress entry by its ID', indicating irreversible removal of data.
Attacks that exploit this kind of access
Deletes a progress entry by its ID. It is categorised as a Destructive tool in the SDOF Knowledge Base MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the SDOF Knowledge Base MCP server in PolicyLayer and add a rule for delete_progress_by_id: 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 SDOF Knowledge Base. Nothing to install.
delete_progress_by_id 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 delete_progress_by_id 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 delete_progress_by_id. 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.
delete_progress_by_id is provided by the SDOF Knowledge Base MCP server (tgf-between-your-legs/sdof-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 →