AI agents call agentKnowledgeProjectRemove to permanently remove resources in Mcp Taskade — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The 'Remove' action on a knowledge project constitutes an irreversible deletion of data. This falls under the Destructive category as it cannot be undone and results in permanent loss of the project. Severity is high because it affects an entire project's knowledge base, though the blast radius is limited to that specific project rather than system-wide or financial impacts.
From the tool's definition Tool name contains 'Remove' and description states 'Remove a knowledge project' — this irreversibly deletes a project and its associated data.
Documented attack patterns abuse exactly the kind of access agentKnowledgeProjectRemove gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Taskade, and nothing reaches the server without passing your rules. This is the rule we recommend for agentKnowledgeProjectRemove:
{
"version": "1",
"default": "deny",
"hide": [
"agentKnowledgeProjectRemove"
]
}agentKnowledgeProjectRemove 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.
Remove a knowledge project. It is categorised as a Destructive tool in the Mcp Taskade MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Mcp Taskade MCP server in PolicyLayer and add a rule for agentKnowledgeProjectRemove: 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 Mcp Taskade. Nothing to install.
agentKnowledgeProjectRemove 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 agentKnowledgeProjectRemove 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 agentKnowledgeProjectRemove. 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.
agentKnowledgeProjectRemove is provided by the Mcp Taskade MCP server (taskade/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 57 Mcp Taskade tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
57 Mcp Taskade tools catalogued and risk-classified — across an index of 42,500+ MCP servers.