Soft-delete a brief block (reversible via brief_restore). Locked blocks are refused.
AI agents call brief_delete to permanently remove resources in Llama — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool performs a delete operation on brief blocks within the deals/briefs management system. While the description indicates the deletion is reversible through the brief_restore function, the tool's core function is to remove data. Destructive category applies because deletion is the primary semantic action, even if recovery is technically possible.
From the tool's definition Tool name 'brief_delete' combined with description stating it 'Soft-delete a brief block'. Although described as 'reversible via brief_restore', the primary action is deletion of data. The tool removes content from the Llama Ventures platform briefs system.
Attacks that exploit this kind of access
Soft-delete a brief block (reversible via brief_restore). Locked blocks are refused. It is categorised as a Destructive tool in the Llama MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Llama MCP server in PolicyLayer and add a rule for brief_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 Llama. Nothing to install.
brief_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 brief_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 brief_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.
brief_delete is provided by the Llama MCP server (llama-ventures/llama-cli). 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 →