mulch
Mulch / Ground-Cover Calculator — Mulch volume for a bed from area and depth — cubic feet, cubic yards, and 2/3 cu ft bag counts, with an optional waste factor and a depth-options table.
This record as markdown: /tools/com-wingmanprotocol-agent-gateway/mulch.md
What mulch does on Gateway
AI agents call mulch 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_in | number | — | Mulch depth in inches (default 3) |
width_ft | number | Yes | Bed width in feet |
length_ft | number | Yes | Bed length in feet |
waste_pct | number | — | Optional waste/overage percent (e.g. 10) |
Parameters from the server's own tool schema.
Why mulch is rated Low
This is a stateless mathematical calculator that takes input parameters (area, depth, waste factor) and returns computed results. It retrieves or derives information without creating, modifying, deleting, or executing any external operations. No data is persisted, no external systems are invoked, and no irreversible actions occur. Classification as Read reflects its query/compute-only nature.
From the tool's definition Tool description states it is a calculator that computes 'Mulch volume for a bed from area and depth' with outputs in various units.
Attacks that exploit this kind of access
The rule that runs mulch 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 mulch, this is the rule to start with:
mulch 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 mulch call is checked against it from then on.
Questions about mulch
Mulch / Ground-Cover Calculator — Mulch volume for a bed from area and depth — cubic feet, cubic yards, and 2/3 cu ft bag counts, with an optional waste factor and a depth-options table. It is categorised as a Read tool in the Gateway MCP Server, which means it retrieves data without modifying state.
mulch accepts 4 parameters: depth_in, width_ft, length_ft, waste_pct. Required: width_ft, length_ft. 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 mulch: 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.
mulch 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 mulch 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 mulch. 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.
mulch 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