markup
Construction Markup Calculator — Bid price, markup and true margin from direct costs, overhead and target margin.
This record as markdown: /tools/com-wingmanprotocol-agent-gateway/markup.md
What markup does on Gateway
AI agents call markup 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 |
|---|---|---|---|
sub_cost | number | — | Subcontractor cost in USD |
bid_price | number | — | Optional: a fixed bid price to reverse-solve margin |
labor_cost | number | — | Direct labor cost in USD |
margin_pct | number | — | Target net margin percent |
overhead_pct | number | — | Overhead as a percent of direct cost |
material_cost | number | — | Material cost in USD |
equipment_cost | number | — | Equipment cost in USD |
Parameters from the server's own tool schema.
Why markup is rated Low
This tool performs financial calculations (markup, margin, bid price) based on input values. It computes and returns numbers without moving money, creating obligations, or modifying any data. Pure calculation/read semantics.
From the tool's definition Construction Markup Calculator — Bid price, markup and true margin from direct costs, overhead and target margin.
Attacks that exploit this kind of access
The rule that runs markup 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 markup, this is the rule to start with:
markup 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 markup call is checked against it from then on.
Questions about markup
Construction Markup Calculator — Bid price, markup and true margin from direct costs, overhead and target margin. It is categorised as a Read tool in the Gateway MCP Server, which means it retrieves data without modifying state.
markup accepts 7 parameters: sub_cost, bid_price, labor_cost, margin_pct, overhead_pct, material_cost, equipment_cost. 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 markup: 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.
markup 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 markup 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 markup. 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.
markup 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