fizzy_pm_report_progress · Fizzy Do MCP: Risk & Policy

WHAT IT DOES

What fizzy_pm_report_progress does on Fizzy Do MCP

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

WHY IT NEEDS A POLICY

Why fizzy_pm_report_progress needs a policy

This tool creates a new comment on a card with structured progress information. It is a write operation (creating/posting data) with no destructive, financial, or execution implications. Misuse could result in spammy or misleading comments, but impact is low and reversible.

From the tool's definition Report progress made on a card by adding a structured comment. Use this to document work done during an AI session.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

fizzy_pm_report_progress Rate-limited

fizzy_pm_report_progress 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_pm_report_progress": {
      "limits": [
        {
          "counter": "fizzy_pm_report_progress_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 Do MCP, so you can run agents against it safely.

FAQ

Questions about fizzy_pm_report_progress

What does the fizzy_pm_report_progress tool do? +

Report progress made on a card by adding a structured comment. Use this to document work done during an AI session. The comment will be formatted as a progress report with: - Summary of work done - Changes made - Any blockers or next steps. 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.

How do I enforce a policy on fizzy_pm_report_progress? +

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

What risk level is fizzy_pm_report_progress? +

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

Can I rate-limit fizzy_pm_report_progress? +

Yes. Add a rate_limit block to the fizzy_pm_report_progress 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_pm_report_progress completely? +

Set action: deny in the PolicyLayer policy for fizzy_pm_report_progress. 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_pm_report_progress? +

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