Clear the shared team board (recall originals are retained until tiered out).
AI agents call knitbrain_team_clear to permanently remove resources in Knitbrain — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool deletes team-wide shared data with permanent effect. Although originals may be temporarily retained, the tool's primary function is irreversible removal of active board state. The 'clear' action on a 'shared team board' demonstrates high blast radius: an AI agent misusing this could erase collaborative work for an entire team, breaking workflows and losing context.
From the tool's definition 'Clear the shared team board' indicates irreversible deletion of shared data from a team collaboration space.
Attacks that exploit this kind of access
Clear the shared team board (recall originals are retained until tiered out). It is categorised as a Destructive tool in the Knitbrain MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Knitbrain MCP server in PolicyLayer and add a rule for knitbrain_team_clear: 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 Knitbrain. Nothing to install.
knitbrain_team_clear 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 knitbrain_team_clear 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 knitbrain_team_clear. 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.
knitbrain_team_clear is provided by the Knitbrain MCP server (pdgit12/knitbrain). 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 →