Clean up system state by removing all tasks
AI agents call clean_state to permanently remove resources in SystemPrompt Coding Agent — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly removes all tasks from the system state. The word 'removing' indicates permanent deletion with no mention of recovery or undo capability. Since it affects ALL tasks (not a selective deletion), the blast radius is high — an AI agent misusing this could wipe the entire task queue/state of an autonomous coding orchestration system.
From the tool's definition Clean up system state by removing all tasks
Documented attack patterns abuse exactly the kind of access clean_state gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and SystemPrompt Coding Agent, and nothing reaches the server without passing your rules. This is the rule we recommend for clean_state:
{
"version": "1",
"default": "deny",
"hide": [
"clean_state"
]
}clean_state disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Clean up system state by removing all tasks. It is categorised as a Destructive tool in the SystemPrompt Coding Agent MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the SystemPrompt Coding Agent MCP server in PolicyLayer and add a rule for clean_state: 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 SystemPrompt Coding Agent. Nothing to install.
clean_state 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 clean_state 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 clean_state. 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.
clean_state is provided by the SystemPrompt Coding Agent MCP server (systempromptio/systemprompt-code-orchestrator). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 8 SystemPrompt Coding Agent tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
8 SystemPrompt Coding Agent tools catalogued and risk-classified — across an index of 42,500+ MCP servers.