concrete
Concrete Calculator — Cubic yards, 60/80-lb bag counts and ready-mix cost for slabs, columns or tubes.
This record as markdown: /tools/com-wingmanprotocol-agent-gateway/concrete.md
What concrete does on Gateway
AI agents call concrete 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 |
|---|---|---|---|
depth | number | — | Tube depth in feet |
shape | string | Yes | Pour shape |
width | number | — | Width in feet (slab/column) |
height | number | — | Column height in feet |
length | number | — | Length in feet (slab/column) |
quantity | integer | — | Number of identical pours (default 1) |
diameter_in | number | — | Tube diameter in inches |
thickness_in | number | — | Slab thickness in inches |
waste_factor | number | — | Waste multiplier (default 1.10) |
price_per_yard | number | — | Ready-mix price per cubic yard (default 150) |
Parameters from the server's own tool schema.
Why concrete is rated Low
This is a pure computational/calculator tool that retrieves information derived from inputs (cubic yards, material costs) but performs no write, destructive, financial transaction, or code execution operations. It has no side effects beyond returning a calculated result.
From the tool's definition The tool description indicates it 'calculates' concrete quantities and costs for construction materials. It performs computations on user-supplied parameters (slab dimensions, bag weights, ready-mix pricing) and returns calculated results without modifying…
Risk signalsHigh parameter count (10 properties)
Attacks that exploit this kind of access
The rule that runs concrete 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 concrete, this is the rule to start with:
concrete 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 concrete call is checked against it from then on.
Questions about concrete
Concrete Calculator — Cubic yards, 60/80-lb bag counts and ready-mix cost for slabs, columns or tubes. It is categorised as a Read tool in the Gateway MCP Server, which means it retrieves data without modifying state.
concrete accepts 10 parameters: depth, shape, width, height, length, quantity, diameter_in, thickness_in, waste_factor, price_per_yard. Required: shape. 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 concrete: 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.
concrete 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 concrete 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 concrete. 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.
concrete 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