Create a new column on a Fizzy board.
AI agents use fizzy_create_column to create or update resources in Fizzy Do MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Fizzy Do MCP environment.
This tool creates and adds a new column to a board, which is a reversible modification of board structure. It does not execute arbitrary code, delete data irreversibly, or involve financial transactions. Creation of board columns is a standard write operation with moderate blast radius—misuse could clutter boards or create confusing project structures, but changes are easily undoable by deletion or modification.
From the tool's definition Tool name 'fizzy_create_column' and description 'Create a new column on a Fizzy board' indicate creation of new structural data within a project management system.
Attacks that exploit this kind of access
Create a new column on a Fizzy board. It is categorised as a Write tool in the Fizzy Do MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Fizzy Do MCP server in PolicyLayer and add a rule for fizzy_create_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 Fizzy Do MCP. Nothing to install.
fizzy_create_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 fizzy_create_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 fizzy_create_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.
fizzy_create_column is provided by the Fizzy Do MCP server (ryanyogan/fizzy-do-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
fizzy_create_column is one line of Fizzy Do's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →