Delete a fact scenario.
AI agents call blawx_fact_scenario_delete to permanently remove resources in Blawx MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool permanently removes a fact scenario from the Blawx system. Deletion operations are irreversible and cannot be undone, making this a Destructive action. The severity is high because accidental deletion of project scenarios could disrupt rule-based logic modeling and require manual recovery or reconstruction.
From the tool's definition Tool name explicitly contains 'delete' and description states 'Delete a fact scenario.' This is an irreversible data deletion operation.
Attacks that exploit this kind of access
Delete a fact scenario. It is categorised as a Destructive tool in the Blawx MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Blawx MCP Server MCP server in PolicyLayer and add a rule for blawx_fact_scenario_delete: 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 Blawx MCP Server. Nothing to install.
blawx_fact_scenario_delete 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 blawx_fact_scenario_delete 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 blawx_fact_scenario_delete. 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.
blawx_fact_scenario_delete is provided by the Blawx MCP Server MCP server (lexpedite/blawx_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →