framing
Wall Framing Calculator — Stud, plate and header counts plus board-feet and cost for a framed wall.
This record as markdown: /tools/com-wingmanprotocol-agent-gateway/framing.md
What framing does on Gateway
AI agents call framing 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 |
|---|---|---|---|
header_size | string | — | Header lumber size (e.g. 2x10) |
header_span | number | — | Header span in feet |
wall_height | number | Yes | Wall height in feet |
wall_length | number | — | Single wall length in feet — used only if total_wall_lf is omitted |
cost_per_bdft | number | — | Lumber cost per board-foot in USD |
total_wall_lf | number | Yes | Linear feet of wall to frame — studs AND plates are sized for this full run |
openings_count | integer | — | Number of door/window openings |
stud_spacing_in | number | — | Stud spacing on-center in inches (default 16) |
Parameters from the server's own tool schema.
Why framing is rated Low
This is a calculator that retrieves or computes derived data (framing material counts and costs) based on user inputs. It performs calculations with no side effects—it does not create, modify, delete, or execute external operations. No data is persisted or irreversibly changed. The tool is purely computational and informational, fitting the Read category as a data retrieval/query tool.
From the tool's definition Tool name 'framing' and description 'Wall Framing Calculator — Stud, plate and header counts plus board-feet and cost for a framed wall' indicate a calculation tool that computes material estimates and costs from input parameters.
Attacks that exploit this kind of access
The rule that runs framing 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 framing, this is the rule to start with:
framing 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 framing call is checked against it from then on.
Questions about framing
Wall Framing Calculator — Stud, plate and header counts plus board-feet and cost for a framed wall. It is categorised as a Read tool in the Gateway MCP Server, which means it retrieves data without modifying state.
framing accepts 8 parameters: header_size, header_span, wall_height, wall_length, cost_per_bdft, total_wall_lf, openings_count, stud_spacing_in. Required: wall_height, total_wall_lf. 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 framing: 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.
framing 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 framing 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 framing. 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.
framing 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