brews_deleteBrew
Delete a Brew from the selected project (POST /v1/brews/delete)
This record as markdown: /tools/onesi-genesis-mcp/brews-deletebrew.md
What brews_deleteBrew does on Genesis
AI agents call brews_deleteBrew to permanently remove resources in Genesis, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
body | object | Yes |
Parameters from the server's own tool schema.
Why brews_deleteBrew is rated Critical
An AI agent that decides to call brews_deleteBrew doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Genesis is gone. There is no undo for destructive operations.
Risk signalsAccepts raw HTML/template content (body)
Attacks that exploit this kind of access
The rule that runs brews_deleteBrew safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Genesis, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For brews_deleteBrew, this is the rule to start with:
brews_deleteBrew is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Genesis, apply this rule, and every brews_deleteBrew call is checked against it from then on.
Questions about brews_deleteBrew
Delete a Brew from the selected project (POST /v1/brews/delete). It is categorised as a Destructive tool in the Genesis MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
brews_deleteBrew accepts 1 parameter: body. Required: body. The full parameter table on this page comes from the server's own tool schema.
Register the Genesis MCP server in PolicyLayer and add a rule for brews_deleteBrew: 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 Genesis. Nothing to install.
brews_deleteBrew is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the brews_deleteBrew 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 brews_deleteBrew. 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.
brews_deleteBrew is provided by the Genesis MCP server (@onesi/genesis-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Genesis, and thousands of servers like it.
Across the catalogue