This record as markdown: /tools/app-businys-mcp-server/delete-blackout.md
What delete_blackout does on Businys
AI agents call delete_blackout to permanently remove resources in Businys, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why delete_blackout is rated Critical
The tool performs irreversible deletion of data (a blackout date record). Blackout dates are typically used to block availability or restrict scheduling during specific periods. Deleting such a record cannot be undone and could have downstream consequences like unintended availability exposure or scheduling conflicts. This fits the Destructive category as it permanently removes data without recovery options.
From the tool's definition Tool name 'delete_blackout' explicitly uses the verb 'delete', and the description confirms it removes a blackout date irreversibly.
Attacks that exploit this kind of access
The rule that runs delete_blackout safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Businys, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_blackout, this is the rule to start with:
delete_blackout 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 Businys, apply this rule, and every delete_blackout call is checked against it from then on.
Questions about delete_blackout
Delete a blackout date. It is categorised as a Destructive tool in the Businys MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Businys MCP server in PolicyLayer and add a rule for delete_blackout: 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 Businys. Nothing to install.
delete_blackout 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 delete_blackout 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 delete_blackout. 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.
delete_blackout is provided by the Businys MCP server (@businys/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Businys, and thousands of servers like it.
Across the catalogue