Get comprehensive context about a project/board for AI decision-making. Includes: board structure, column workflow, and card statistics. Use this before starting work on a board to understand the project state.
AI agents call fizzy_pm_project_context to retrieve information from Fizzy Do MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries project/board information for context and decision-making purposes. It performs no modifications, deletions, or external operations. It is purely informational, making it a Read category tool with low severity since context retrieval poses minimal risk even if misused by an AI agent.
From the tool's definition Tool description states it 'Get[s] comprehensive context' and 'Includes: board structure, column workflow, and card statistics.' The verb 'Get' and the framing 'Use this before starting work' indicate data retrieval with no side effects.
Attacks that exploit this kind of access
Get comprehensive context about a project/board for AI decision-making. Includes: board structure, column workflow, and card statistics. Use this before starting work on a board to understand the project state. It is categorised as a Read tool in the Fizzy Do MCP MCP Server, which means it retrieves data without modifying state.
Register the Fizzy Do MCP server in PolicyLayer and add a rule for fizzy_pm_project_context: 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_project_context is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the fizzy_pm_project_context 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_project_context. 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_project_context 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 →