paver
Paver Calculator — Paver count, base material and cost for a patio/walkway, including cutouts and waste.
This record as markdown: /tools/com-wingmanprotocol-agent-gateway/paver.md
What paver does on Gateway
AI agents call paver 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 |
|---|---|---|---|
shape | string | Yes | Area shape |
width | number | — | Width in feet |
length | number | — | Length in feet |
pattern | string | — | Laying pattern |
diameter | number | — | Diameter for circular area in feet |
waste_pct | number | — | Waste allowance percent |
paver_size | string | — | Named paver size |
outer_width | number | — | Outer width for L-shape in feet |
cutout_width | number | — | Cutout width in feet |
outer_length | number | — | Outer length for L-shape in feet |
base_depth_in | number | Yes | Base material depth in inches |
cutout_length | number | — | Cutout length in feet |
Parameters from the server's own tool schema.
Why paver is rated Low
This tool performs mathematical calculations on user-provided inputs (patio dimensions, cutout specifications) and returns estimated results (paver count, material quantities, cost estimates). It retrieves/computes data without persisting state changes, modifying external systems, or executing side effects.
From the tool's definition Tool name 'paver' and description 'Paver Calculator — Paver count, base material and cost for a patio/walkway, including cutouts and waste.' indicates a calculation/estimation tool that computes quantities and costs based on input dimensions.
Risk signalsHigh parameter count (15 properties)
Attacks that exploit this kind of access
The rule that runs paver 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 paver, this is the rule to start with:
paver 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 paver call is checked against it from then on.
Questions about paver
Paver Calculator — Paver count, base material and cost for a patio/walkway, including cutouts and waste. It is categorised as a Read tool in the Gateway MCP Server, which means it retrieves data without modifying state.
paver accepts 12 parameters: shape, width, length, pattern, diameter, waste_pct, paver_size, outer_width, cutout_width, outer_length, base_depth_in, cutout_length. Required: shape, base_depth_in. 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 paver: 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.
paver 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 paver 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 paver. 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.
paver 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