This record as markdown: /tools/firebase-genkit/removetask.md
What removeTask does on Genkit MCP
AI agents call removeTask to permanently remove resources in Genkit MCP, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why removeTask is rated Critical
This tool permanently deletes task records by ID. Task removal cannot be undone without external recovery mechanisms, making it destructive rather than merely a write operation. The high severity reflects that an AI agent misusing this tool could delete important user tasks. Confidence is high because the description clearly indicates removal/deletion semantics.
From the tool's definition Tool name 'removeTask' and description 'Remove a task from the list by its ID' indicate irreversible deletion of data.
Attacks that exploit this kind of access
The rule that runs removeTask safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Genkit MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For removeTask, this is the rule to start with:
removeTask is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Genkit MCP, apply this rule, and every removeTask call is checked against it from then on.
Questions about removeTask
Remove a task from the list by its ID. It is categorised as a Destructive tool in the Genkit MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Genkit MCP server in PolicyLayer and add a rule for removeTask: 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 Genkit MCP. Nothing to install.
removeTask 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 removeTask 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 removeTask. 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.
removeTask is provided by the Genkit MCP server (genkit-ai/genkit). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Genkit, and thousands of servers like it.
Across the catalogue