raised_bed
Raised-Bed Soil Calculator — Soil volume for one or more raised beds (cu ft / cu yd / bag counts) plus a standard 60/30/10 topsoil-compost-aeration mix breakdown.
This record as markdown: /tools/com-wingmanprotocol-agent-gateway/raised-bed.md
What raised_bed does on Gateway
AI agents call raised_bed 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 |
|---|---|---|---|
beds | integer | — | Number of identical beds (default 1) |
width_ft | number | Yes | Bed width in feet |
height_in | number | — | Bed height/depth in inches (default 10) |
length_ft | number | Yes | Bed length in feet |
Parameters from the server's own tool schema.
Why raised_bed is rated Low
The raised-bed soil calculator accepts dimensional inputs and returns computed metrics (volume, bag counts, mix ratios). This is a read-only calculation tool with no side effects on data or systems. The low severity reflects that misuse would at most produce incorrect gardening estimates, with no harmful external effects.
From the tool's definition Tool description explicitly states it 'calculates' soil volume and provides a 'breakdown' — pure computation and retrieval of numerical results based on input dimensions. No creation, modification, deletion, execution, or financial operations involved.
Attacks that exploit this kind of access
The rule that runs raised_bed 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 raised_bed, this is the rule to start with:
raised_bed 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 raised_bed call is checked against it from then on.
Questions about raised_bed
Raised-Bed Soil Calculator — Soil volume for one or more raised beds (cu ft / cu yd / bag counts) plus a standard 60/30/10 topsoil-compost-aeration mix breakdown. It is categorised as a Read tool in the Gateway MCP Server, which means it retrieves data without modifying state.
raised_bed accepts 4 parameters: beds, width_ft, height_in, length_ft. 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 raised_bed: 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.
raised_bed 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 raised_bed 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 raised_bed. 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.
raised_bed 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