fizzy_tag_card · Fizzy MCP Server MCP: Risk & Policy

WHAT IT DOES

What fizzy_tag_card does on Fizzy MCP Server

AI agents use fizzy_tag_card 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.

WHY IT NEEDS A POLICY

Why fizzy_tag_card needs a policy

This tool modifies card metadata (tags) in a reversible way — tags can be re-added or removed again at any time. It neither deletes data irreversibly nor executes code, making Write the appropriate category. The blast radius is low since only tag metadata is affected.

From the tool's definition 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.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

fizzy_tag_card Rate-limited

fizzy_tag_card 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "fizzy_tag_card": {
      "limits": [
        {
          "counter": "fizzy_tag_card_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Fizzy MCP Server, so you can run agents against it safely.

FAQ

Questions about fizzy_tag_card

What does the fizzy_tag_card tool do? +

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. 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.

How do I enforce a policy on fizzy_tag_card? +

Register the Fizzy MCP Server MCP server in PolicyLayer and add a rule for fizzy_tag_card: 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.

What risk level is fizzy_tag_card? +

fizzy_tag_card is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit fizzy_tag_card? +

Yes. Add a rate_limit block to the fizzy_tag_card 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.

How do I block fizzy_tag_card completely? +

Set action: deny in the PolicyLayer policy for fizzy_tag_card. 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.

What MCP server provides fizzy_tag_card? +

fizzy_tag_card 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.