AI agents invoke deal_refresh_brief to trigger actions in Llama. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool executes a backend operation (re-evaluation logic) rather than passively reading data. While not destructive or financial, it performs a side-effecting action that processes and potentially updates deal state. The high severity reflects that triggering unsolicited re-evaluations could disrupt deal workflows, cause computational overhead, or produce unintended state changes.
From the tool's definition Tool name 'deal_refresh_brief' with description 'Trigger a stale-section re-evaluation of a deal' indicates execution of a backend process.
Attacks that exploit this kind of access
Trigger a stale-section re-evaluation of a deal. It is categorised as a Execute tool in the Llama MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Llama MCP server in PolicyLayer and add a rule for deal_refresh_brief: 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.
deal_refresh_brief is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the deal_refresh_brief 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 deal_refresh_brief. 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.
deal_refresh_brief 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 →