Clear stored run history for a task but keep the schedule active. Use when the user wants to reset success/error logs for a new reporting window.
AI agents call clear_task_history to permanently remove resources in Schedule Task MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly deletes stored run history and logs for a task. While the task itself remains active, the historical data (success/error logs) is permanently purged. This qualifies as Destructive since the deleted history cannot be recovered. Severity is medium because it affects audit/diagnostic data but not the task schedule itself or production data.
From the tool's definition 'Clear stored run history for a task' and 'reset success/error logs' — permanently removes historical run data with no indication of reversibility
Attacks that exploit this kind of access
Clear stored run history for a task but keep the schedule active. Use when the user wants to reset success/error logs for a new reporting window. It is categorised as a Destructive tool in the Schedule Task MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Schedule Task MCP server in PolicyLayer and add a rule for clear_task_history: 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 Schedule Task MCP. Nothing to install.
clear_task_history 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 clear_task_history 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 clear_task_history. 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.
clear_task_history is provided by the Schedule Task MCP server (liao1fan/schedule-task-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 →