AI agents invoke deal_enrich 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.
The tool explicitly 'runs' a planner/trigger, indicating it executes an external operation or workflow. It's not a simple read or write — it triggers an automated process (enrichment pipeline) whose side effects depend on the deal argument and the underlying system. This falls squarely in Execute.
From the tool's definition "Run the Llama Command deal enrichment planner/trigger for one deal"
Attacks that exploit this kind of access
Run the Llama Command deal enrichment planner/trigger for one 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_enrich: 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_enrich 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_enrich 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_enrich. 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_enrich 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 →