Remove a widget from a Kanban board
AI agents call remove_board_widget to permanently remove resources in OpenProject MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool removes/deletes a widget configuration from a Kanban board. While the blast radius is scoped to a single widget (not entire data), the action is irreversible—once removed, the widget configuration and its state are lost. This qualifies as Destructive rather than Write because removal cannot be easily reversed without recreating the widget and its settings.
From the tool's definition Tool name 'remove_board_widget' uses the verb 'remove', which indicates deletion of a board widget. The description states it will 'Remove a widget from a Kanban board', explicitly performing an irreversible deletion action.
Attacks that exploit this kind of access
Remove a widget from a Kanban board. It is categorised as a Destructive tool in the OpenProject MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the OpenProject MCP Server MCP server in PolicyLayer and add a rule for remove_board_widget: 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 OpenProject MCP Server. Nothing to install.
remove_board_widget 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 remove_board_widget 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 remove_board_widget. 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.
remove_board_widget is provided by the OpenProject MCP Server MCP server (widjis/mcp-openproject). 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 →