deal_agent_run · Llama MCP: Risk & Policy

WHAT IT DOES

What deal_agent_run does on Llama

AI agents invoke deal_agent_run 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.

WHY IT NEEDS A POLICY

Why deal_agent_run needs a policy

The verb 'Run' combined with 'Command' clearly indicates code or command execution rather than simple data retrieval or modification. This falls under Execute category as it triggers operations with argument-dependent effects. High severity due to potential for uncontrolled command execution on the platform's deal management system.

From the tool's definition Tool name 'deal_agent_run' with description 'Run Llama Command' indicates execution of commands or operations. The context of a deals/briefs management platform suggests this triggers external operations whose effects depend on runtime arguments.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

deal_agent_run Rate-limited

deal_agent_run stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "deal_agent_run": {
      "limits": [
        {
          "counter": "deal_agent_run_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Llama, so you can run agents against it safely.

FAQ

Questions about deal_agent_run

What does the deal_agent_run tool do? +

Run Llama Command. 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.

How do I enforce a policy on deal_agent_run? +

Register the Llama MCP server in PolicyLayer and add a rule for deal_agent_run: 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.

What risk level is deal_agent_run? +

deal_agent_run is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit deal_agent_run? +

Yes. Add a rate_limit block to the deal_agent_run 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.

How do I block deal_agent_run completely? +

Set action: deny in the PolicyLayer policy for deal_agent_run. 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.

What MCP server provides deal_agent_run? +

deal_agent_run 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.