bolsa_notifications_delete
Delete notification
This record as markdown: /tools/cargoffer-bolsa-de-carga-mcp/bolsa-notifications-delete.md
What bolsa_notifications_delete does on Bolsa De Carga
AI agents call bolsa_notifications_delete to permanently remove resources in Bolsa De Carga, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why bolsa_notifications_delete is rated Critical
This tool irreversibly deletes notification records, which cannot be undone. While the blast radius is limited to notifications rather than critical freight data, deletion of notifications could cause loss of important alerts about load updates, driver assignments, or delivery status changes in a logistics context. This falls under Destructive rather than Write because the action cannot be reversed.
From the tool's definition Tool name 'bolsa_notifications_delete' explicitly specifies a delete operation on notifications. The description 'Delete notification' confirms irreversible removal of data.
Attacks that exploit this kind of access
The rule that runs bolsa_notifications_delete safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Bolsa De Carga, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For bolsa_notifications_delete, this is the rule to start with:
bolsa_notifications_delete 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 Bolsa De Carga, apply this rule, and every bolsa_notifications_delete call is checked against it from then on.
Questions about bolsa_notifications_delete
Delete notification. It is categorised as a Destructive tool in the Bolsa De Carga MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Bolsa De Carga MCP server in PolicyLayer and add a rule for bolsa_notifications_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 Bolsa De Carga. Nothing to install.
bolsa_notifications_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 bolsa_notifications_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 bolsa_notifications_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.
bolsa_notifications_delete is provided by the Bolsa De Carga MCP server (cargoffer/bolsa_de_carga-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Bolsa De Carga, and thousands of servers like it.
Across the catalogue