asphalt
Asphalt Calculator — Tons of asphalt, loose cubic yards, truckloads and sub-base from driveway/lot dimensions.
This record as markdown: /tools/com-wingmanprotocol-agent-gateway/asphalt.md
What asphalt does on Gateway
AI agents call asphalt 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 | Width in feet |
length | number | Yes | Length in feet |
depth_in | number | Yes | Asphalt depth in inches |
price_per_ton | number | — | Asphalt price per ton in USD |
density_lb_per_cf | number | — | Asphalt density in lb/ft3 (default ~145) |
sub_base_depth_in | number | — | Gravel sub-base depth in inches |
Parameters from the server's own tool schema.
Why asphalt is rated Low
This is a calculation utility that takes geometric inputs (driveway/lot dimensions) and returns computed results. It retrieves or derives data without creating, modifying, deleting, executing external commands, or moving funds. The tool is read-only in nature.
From the tool's definition The tool is described as a calculator that computes "tons of asphalt, loose cubic yards, truckloads and sub-base from driveway/lot dimensions." It performs mathematical calculations based on input dimensions with no side effects.
Attacks that exploit this kind of access
The rule that runs asphalt 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 asphalt, this is the rule to start with:
asphalt 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 asphalt call is checked against it from then on.
Questions about asphalt
Asphalt Calculator — Tons of asphalt, loose cubic yards, truckloads and sub-base from driveway/lot dimensions. It is categorised as a Read tool in the Gateway MCP Server, which means it retrieves data without modifying state.
asphalt accepts 6 parameters: width, length, depth_in, price_per_ton, density_lb_per_cf, sub_base_depth_in. Required: width, length, 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 asphalt: 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.
asphalt 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 asphalt 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 asphalt. 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.
asphalt 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