rebar
Rebar Calculator — Total rebar length, bar count and cost for a grid from slab dimensions and spacing.
This record as markdown: /tools/com-wingmanprotocol-agent-gateway/rebar.md
What rebar does on Gateway
AI agents call rebar 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 |
|---|---|---|---|
width | number | Yes | Slab width in feet |
length | number | Yes | Slab length in feet |
lap_pct | number | — | Lap/overlap allowance percent |
bar_size | string | — | Rebar size designation (e.g. #4, #5) |
spacing_in | number | — | Grid spacing in inches |
cost_per_lf | number | — | Cost per linear foot in USD |
Parameters from the server's own tool schema.
Why rebar is rated Low
This is a pure calculation tool that transforms user inputs into outputs without side effects. It falls clearly under the Read category as it only computes and returns information based on provided dimensions and spacing parameters. The low severity reflects the minimal risk from misuse—an AI agent could only provide incorrect input dimensions, resulting in wrong calculations, not system damage or data loss.
From the tool's definition The tool 'rebar' performs calculations based on input parameters (slab dimensions and spacing) and returns computed results (total rebar length, bar count and cost).
Attacks that exploit this kind of access
The rule that runs rebar 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 rebar, this is the rule to start with:
rebar 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 rebar call is checked against it from then on.
Questions about rebar
Rebar Calculator — Total rebar length, bar count and cost for a grid from slab dimensions and spacing. It is categorised as a Read tool in the Gateway MCP Server, which means it retrieves data without modifying state.
rebar accepts 6 parameters: width, length, lap_pct, bar_size, spacing_in, cost_per_lf. Required: width, length. 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 rebar: 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.
rebar 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 rebar 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 rebar. 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.
rebar 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