Add a widget (column) to a Kanban board
AI agents use add_board_widget to create or update resources in OpenProject MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your OpenProject MCP Server environment.
This tool creates a new board widget/column, which is a Write operation — it modifies the Kanban board configuration reversibly. It does not delete data (Destructive), execute arbitrary code (Execute), involve financial transactions (Financial), or merely read data (Read). Severity is medium because misuse could clutter the board or affect team workflow, but the impact is localized to board UI and easily undone.
From the tool's definition Tool description states 'Add a widget (column) to a Kanban board' — this creates or modifies board structure by adding a new column.
Attacks that exploit this kind of access
Add a widget (column) to a Kanban board. It is categorised as a Write tool in the OpenProject MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the OpenProject MCP Server MCP server in PolicyLayer and add a rule for add_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.
add_board_widget is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the add_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 add_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.
add_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 →