update_kanban_column
Rename a column, recolour it, or mark it as the done column. Cards entering a done column count as completed and award XP.
This record as markdown: /tools/com-idosgames-platform/update-kanban-column.md
What update_kanban_column does on iDos Games
AI agents use update_kanban_column to create or update resources in iDos Games, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your iDos Games environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | — | New name (optional). |
color | string | — | New accent colour (optional). |
is_done | boolean | — | Whether this is the done column (optional). |
column_id | string | Yes | Column to change. |
project_id | string | Yes | Board the column belongs to. |
Parameters from the server's own tool schema.
Why update_kanban_column is rated Medium
An AI agent can call update_kanban_column faster than any human can review: one bad instruction and it creates or modifies resources in iDos Games by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs update_kanban_column safely
PolicyLayer is an MCP gateway: it sits between your AI agents and iDos Games, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For update_kanban_column, this is the rule to start with:
update_kanban_column stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect iDos Games, apply this rule, and every update_kanban_column call is checked against it from then on.
Questions about update_kanban_column
Rename a column, recolour it, or mark it as the done column. Cards entering a done column count as completed and award XP. It is categorised as a Write tool in the iDos Games MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
update_kanban_column accepts 5 parameters: name, color, is_done, column_id, project_id. Required: column_id, project_id. The full parameter table on this page comes from the server's own tool schema.
Register the iDos Games MCP server in PolicyLayer and add a rule for update_kanban_column: 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 iDos Games. Nothing to install.
update_kanban_column 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 update_kanban_column 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 update_kanban_column. 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.
update_kanban_column is provided by the iDos Games MCP server (https://site.idosgames.com/api/v2/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on iDos Games, and thousands of servers like it.
This server
Across the catalogue