End a work session on a card with a summary. This wraps up the session by: - Adding a summary comment with what was accomplished - Optionally marking steps as complete - Optionally closing the card if work is done Use this after completing work on a card.
AI agents use fizzy_pm_end_session 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 primarily writes data (adds a summary comment, marks steps complete, optionally closes a card). Closing a card could be considered mildly destructive but is typically reversible in task management systems (cards can be reopened). The dominant action is writing/updating state rather than irreversible deletion, so Write is the most appropriate category.
From the tool's definition End a work session on a card with a summary... Adding a summary comment with what was accomplished... Optionally marking steps as complete... Optionally closing the card if work is done
Attacks that exploit this kind of access
End a work session on a card with a summary. This wraps up the session by: - Adding a summary comment with what was accomplished - Optionally marking steps as complete - Optionally closing the card if work is done Use this after completing work on a card. 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_pm_end_session: 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_pm_end_session 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_pm_end_session 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_pm_end_session. 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_pm_end_session 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.
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 →