change_order
Change Order Calculator — Priced change order with overhead, profit and revised contract total.
This record as markdown: /tools/com-wingmanprotocol-agent-gateway/change-order.md
What change_order does on Gateway
AI agents call change_order 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 |
|---|---|---|---|
labor_rate | number | — | Labor rate per hour in USD |
profit_pct | number | — | Profit percent on the change |
labor_hours | number | — | Added labor hours |
overhead_pct | number | — | Overhead percent on the change |
material_cost | number | — | Added material cost in USD |
original_contract | number | Yes | Original contract amount in USD |
schedule_impact_days | number | — | Added days to the schedule |
Parameters from the server's own tool schema.
Why change_order is rated Low
The tool appears to be a calculator that computes financial figures (overhead, profit, revised contract total) for a change order. It performs calculations and returns results rather than moving money or committing financial obligations. It is likely a read/compute operation with no side effects, similar to other calculators described in the server (board_feet, concrete, etc.).
From the tool's definition Change Order Calculator — Priced change order with overhead, profit and revised contract total.
Attacks that exploit this kind of access
The rule that runs change_order 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 change_order, this is the rule to start with:
change_order 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 change_order call is checked against it from then on.
Questions about change_order
Change Order Calculator — Priced change order with overhead, profit and revised contract total. It is categorised as a Read tool in the Gateway MCP Server, which means it retrieves data without modifying state.
change_order accepts 7 parameters: labor_rate, profit_pct, labor_hours, overhead_pct, material_cost, original_contract, schedule_impact_days. Required: original_contract. 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 change_order: 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.
change_order 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 change_order 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 change_order. 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.
change_order 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