Create a new column on a Fizzy board.
AI agents use fizzy_create_column to create or update resources in Fizzy MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Fizzy MCP Server environment.
This tool creates a new column (a structural organizational element) on a board, which is a reversible write operation. It modifies the board structure but does not execute arbitrary code, delete data, move money, or retrieve sensitive information. The impact is scoped to adding a new organizational unit, making it a low-severity Write action. Confidence is high because the intent is explicit and unambiguous.
From the tool's definition Tool name 'fizzy_create_column' and description 'Create a new column on a Fizzy board' indicate creation of a new structural element within the task 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 MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Fizzy MCP Server 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 MCP Server. 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 MCP Server MCP server (ryanyogan/fizzy-mcp). 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 →