clear_finished_tasks

A destructive tool on the ProAgentStore MCP server.

SERVERProAgentStore SOURCEhttps://mcp.proagentstore.online/mcp

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/io-github-proagentstore-platform/clear-finished-tasks.md

WHAT IT DOES

What clear_finished_tasks does on ProAgentStore

AI agents call clear_finished_tasks to permanently remove resources in ProAgentStore, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why clear_finished_tasks is rated Critical

'Clear finished tasks' likely irreversibly removes completed task records from the system.

From the tool's definition uninformative description

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs clear_finished_tasks safely

PolicyLayer is an MCP gateway: it sits between your AI agents and ProAgentStore, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For clear_finished_tasks, this is the rule to start with:

clear_finished_tasks Hidden

clear_finished_tasks is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "clear_finished_tasks"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect ProAgentStore, apply this rule, and every clear_finished_tasks call is checked against it from then on.

FAQ

Questions about clear_finished_tasks

What does the clear_finished_tasks tool do? +

clear_finished_tasks is a destructive tool on the ProAgentStore MCP server. It is categorised as a Destructive tool in the ProAgentStore MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on clear_finished_tasks? +

Register the ProAgentStore MCP server in PolicyLayer and add a rule for clear_finished_tasks: 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 ProAgentStore. Nothing to install.

What risk level is clear_finished_tasks? +

clear_finished_tasks is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit clear_finished_tasks? +

Yes. Add a rate_limit block to the clear_finished_tasks 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.

How do I block clear_finished_tasks completely? +

Set action: deny in the PolicyLayer policy for clear_finished_tasks. 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.

What MCP server provides clear_finished_tasks? +

clear_finished_tasks is provided by the ProAgentStore MCP server (https://mcp.proagentstore.online/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on ProAgentStore, and thousands of servers like it.

This server

All 243 ProAgentStore tools → Critical-risk tools on this server →

Across the catalogue

clear_project_index on ACE-MCP →clear_renders on Why Did You Render →knowledge_clear on Templonix Lite MCP Server →clear_scan on Frida Game Hacking MCP → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Blast radius →Tool call approval →