Fizzy MCP Server

40 tools. 26 can modify or destroy data without limits.

4 destructive tools with no built-in limits. Policy required.

Last updated:

26 can modify or destroy data
14 read-only
40 tools total

Community server · catalogue entry verified 03/07/2026

How to control Fizzy MCP Server ↓

What Fizzy MCP Server exposes to your agents

Read (14) Write / Execute (22) Destructive / Financial (4)
Critical Risk

The most dangerous Fizzy MCP Server tools

26 of Fizzy MCP Server's 40 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

How to control Fizzy MCP Server

PolicyLayer is an MCP gateway — it sits between your AI agents and Fizzy MCP Server, and nothing reaches the server without passing your rules. These are the rules we recommend:

Deny destructive operations
{
  "fizzy_delete_board": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations
{
  "fizzy_assign_card": {
    "limits": [
      {
        "counter": "fizzy_assign_card_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations
{
  "fizzy_get_account": {
    "limits": [
      {
        "counter": "fizzy_get_account_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

  1. Create a free account and register Fizzy MCP Server — nothing to install.
  2. Add these rules — paste them, or build them visually. Tune the limits to your setup.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
ENFORCE POLICY ON FIZZY →

Instant setup, no code required.

All 40 Fizzy MCP Server tools

WRITE 22 tools
Write fizzy_assign_card Toggle assignment of a user to a Fizzy card. If the user is not assigned, they will be added. If they are, the Write fizzy_close_card Close (complete) a Fizzy card, marking it as done. Write fizzy_create_board Create a new Fizzy board. Write fizzy_create_card Create a new Fizzy card on a board. Write fizzy_create_column Create a new column on a Fizzy board. Write fizzy_create_comment Add a comment to a Fizzy card. Write fizzy_mark_golden Mark a Fizzy card as golden (important). Write fizzy_pin_card Pin a Fizzy card for quick access. Write fizzy_postpone_card Move a Fizzy card to Write fizzy_publish_board Publish a Fizzy board, making it publicly accessible via a shareable link. Write fizzy_reopen_card Reopen a closed Fizzy card. Write fizzy_tag_card Toggle a tag on a Fizzy card. If the tag is not on the card, it will be added. If it is, it will be removed. Write fizzy_triage_card Move a Fizzy card into a specific column on the board. Write fizzy_unmark_golden Remove golden status from a Fizzy card. Write fizzy_unpin_card Unpin a Fizzy card. Write fizzy_unpublish_board Unpublish a Fizzy board, removing public access. Write fizzy_untriage_card Send a Fizzy card back to triage, removing it from its column. Write fizzy_unwatch_card Unsubscribe from notifications for a Fizzy card. Write fizzy_update_board Update an existing Fizzy board. Only board administrators can update boards. Write fizzy_update_card Update an existing Fizzy card. Write fizzy_update_column Update a column on a Fizzy board. Write fizzy_update_comment Update a comment. Only the comment creator can update their comments.

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

Questions about Fizzy MCP Server

Can an AI agent delete data through the Fizzy MCP Server MCP server? +

Yes. The Fizzy MCP Server server exposes 4 destructive tools including fizzy_delete_board, fizzy_delete_card, fizzy_delete_column. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Fizzy MCP Server? +

The Fizzy MCP Server server has 22 write tools including fizzy_assign_card, fizzy_close_card, fizzy_create_board. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Fizzy MCP Server.

How many tools does the Fizzy MCP Server MCP server expose? +

40 tools across 3 categories: Destructive, Read, Write. 14 are read-only. 26 can modify, create, or delete data.

How do I enforce a policy on Fizzy MCP Server? +

Register the Fizzy MCP Server MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Fizzy MCP Server tool call.

Deterministic rules across all 40 Fizzy MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Instant setup, no code required.

40 Fizzy MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.