pomodoro_planner
Pomodoro Focus Planner — Lay out a Pomodoro focus/break schedule from a session count or work-minute budget: focus time, break time, sessions and wall-clock end.
This record as markdown: /tools/com-wingmanprotocol-agent-gateway/pomodoro-planner.md
What pomodoro_planner does on Gateway
AI agents call pomodoro_planner to retrieve information from Gateway without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
sessions | integer | — | Number of focus sessions (overrides total_work_minutes) |
focus_len | integer | — | Focus session length in minutes (default 25) |
long_break | integer | — | Long break length in minutes (default 15) |
short_break | integer | — | Short break length in minutes (default 5) |
cycles_per_long | integer | — | Focus sessions between long breaks (default 4) |
total_work_minutes | number | — | Total focus budget in minutes (used if sessions omitted) |
Parameters from the server's own tool schema.
Why pomodoro_planner is rated Low
The tool computes and returns a planned schedule based on input parameters. It performs a calculation/projection with no side effects—no data is written, deleted, or executed. It is purely a read/compute operation similar to the other calculators listed as sibling tools.
From the tool's definition Lay out a Pomodoro focus/break schedule from a session count or work-minute budget: focus time, break time, sessions and wall-clock end
Attacks that exploit this kind of access
The rule that runs pomodoro_planner safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Gateway, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For pomodoro_planner, this is the rule to start with:
pomodoro_planner is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Gateway, apply this rule, and every pomodoro_planner call is checked against it from then on.
Questions about pomodoro_planner
Pomodoro Focus Planner — Lay out a Pomodoro focus/break schedule from a session count or work-minute budget: focus time, break time, sessions and wall-clock end. It is categorised as a Read tool in the Gateway MCP Server, which means it retrieves data without modifying state.
pomodoro_planner accepts 6 parameters: sessions, focus_len, long_break, short_break, cycles_per_long, total_work_minutes. The full parameter table on this page comes from the server's own tool schema.
Register the Gateway MCP server in PolicyLayer and add a rule for pomodoro_planner: 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 Gateway. Nothing to install.
pomodoro_planner 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 pomodoro_planner 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 pomodoro_planner. 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.
pomodoro_planner is provided by the Gateway MCP server (https://wingmanprotocol.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Gateway, and thousands of servers like it.
This server
Across the catalogue