draw_schedule
Construction Draw Schedule Calculator — Milestone draw schedule (deposit, draws, retainage) for a fixed-price construction contract.
This record as markdown: /tools/com-wingmanprotocol-agent-gateway/draw-schedule.md
What draw_schedule does on Gateway
AI agents use draw_schedule to create or update resources in Gateway, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Gateway environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
num_draws | integer | — | Number of progress draws |
deposit_pct | number | — | Up-front deposit percent |
retainage_pct | number | — | Retainage percent held until completion |
contract_amount | number | Yes | Total contract amount in USD |
Parameters from the server's own tool schema.
Why draw_schedule is rated Medium
The tool computes and outputs a draw schedule (deposit, draws, retainage) for construction contracts. This is a Write operation—it generates structured financial planning data that will be stored or transmitted. While it involves financial calculations, it does not move money, process payments, or commit financial obligations itself (Financial category); instead, it prepares data that informs financial decisions.
From the tool's definition Tool creates/generates a 'Milestone draw schedule' for construction contracts, implying data generation and persistence of financial planning documents.
Attacks that exploit this kind of access
The rule that runs draw_schedule 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 draw_schedule, this is the rule to start with:
draw_schedule 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Gateway, apply this rule, and every draw_schedule call is checked against it from then on.
Questions about draw_schedule
Construction Draw Schedule Calculator — Milestone draw schedule (deposit, draws, retainage) for a fixed-price construction contract. It is categorised as a Write tool in the Gateway MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
draw_schedule accepts 4 parameters: num_draws, deposit_pct, retainage_pct, contract_amount. Required: contract_amount. 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 draw_schedule: 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.
draw_schedule 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 draw_schedule 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 draw_schedule. 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.
draw_schedule 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