garden_planting_calendar
Garden Planting Calendar — From your last spring frost date, get a per-crop schedule: when to start seeds indoors, when to plant out, and approximate harvest start.
This record as markdown: /tools/com-wingmanprotocol-agent-gateway/garden-planting-calendar.md
What garden_planting_calendar does on Gateway
AI agents call garden_planting_calendar 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 |
|---|---|---|---|
crops | array | — | Optional crop names to include; omit for the full set |
last_frost | string | Yes | Last spring frost date, ISO format e.g. '2026-04-15' |
Parameters from the server's own tool schema.
Why garden_planting_calendar is rated Low
This tool takes a frost date as input and returns planting schedule information. It performs a read/calculation operation with no side effects, no data modification, no code execution, and no financial implications. It is a pure informational/calculator tool.
From the tool's definition 'get a per-crop schedule: when to start seeds indoors, when to plant out, and approximate harvest start' — purely informational, retrieves calculated schedule data
Attacks that exploit this kind of access
The rule that runs garden_planting_calendar 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 garden_planting_calendar, this is the rule to start with:
garden_planting_calendar 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 garden_planting_calendar call is checked against it from then on.
Questions about garden_planting_calendar
Garden Planting Calendar — From your last spring frost date, get a per-crop schedule: when to start seeds indoors, when to plant out, and approximate harvest start. It is categorised as a Read tool in the Gateway MCP Server, which means it retrieves data without modifying state.
garden_planting_calendar accepts 2 parameters: crops, last_frost. Required: last_frost. 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 garden_planting_calendar: 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.
garden_planting_calendar 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 garden_planting_calendar 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 garden_planting_calendar. 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.
garden_planting_calendar 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