Llama

58 tools. 34 can modify or destroy data without limits.

6 destructive tools with no built-in limits. Policy required.

Last updated:

34 can modify or destroy data
24 read-only
58 tools total

Community server · catalogue entry verified 30/06/2026

How to control Llama ↓

What Llama exposes to your agents

Read (24) Write / Execute (28) Destructive / Financial (6)
Critical Risk

The most dangerous Llama tools

34 of Llama's 58 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

How to control Llama

PolicyLayer is an MCP gateway — it sits between your AI agents and Llama, and nothing reaches the server without passing your rules. These are the rules we recommend:

Block financial tools by default
{
  "pitch_finalize": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Requires human approval."
      }
    ]
  }
}

Financial tools should be explicitly enabled per use case, not open by default.

Deny destructive operations
{
  "brief_delete": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations
{
  "brief_add_callout": {
    "limits": [
      {
        "counter": "brief_add_callout_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations
{
  "agent_bootstrap": {
    "limits": [
      {
        "counter": "agent_bootstrap_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

  1. Create a free account and register Llama — nothing to install.
  2. Add these rules — paste them, or build them visually. Tune the limits to your setup.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
ENFORCE POLICY ON LLAMA →

Instant setup, no code required.

All 58 Llama tools

WRITE 24 tools
Write brief_add_callout Prepend a callout block to a deal brief. Use for emphasized insights or warnings. Write brief_add_link Prepend a link block to a deal brief. Server fetches og:image + title via /api/link-preview. Write brief_add_text Prepend a markdown text block to a deal brief. Supports markdown + mermaid diagrams. Write brief_edit Edit an existing brief block in place. Pass only the fields you want to change Write brief_restore Restore a soft-deleted brief block. Write brief_restore_version Restore a brief block to a specific historical version (find historyId via brief_history). Write deal_create Create a new pipeline deal. Source defaults to the caller Write deal_fact_add Record a factual claim about a deal. RESPONSIBILITY: set Write deal_update Update a single whitelisted field on a deal. Writable fields: status, theirStage, Write html_docs_create Create a NEW named document slot on a deal (metadata only — Write html_restore Restore an old HTML version by copying it forward as a new Write html_upload Upload (PUT) a new HTML version for a SPECIFIC DEAL Write html_upload_bundle Legacy small inline upload for HTML + binary assets as one atomic version. Write html_upload_file Agent-safe HTML upload from a LOCAL FILE PATH. Use this instead Write memo_save Save hand-written HTML as a manual override for a deal Write mentions_resolve Mark an @-mention as resolved (clears it from the recipient Write pitch_send_message Relay a message from the founder to Llama Ventures Write pitch_start Start a new pitch session with Llama Ventures Write pitch_upload_file Attach a file (deck, one-pager, deck PDF, screenshot, etc.) to the Write post Post a message to a deal Write record_eval_feedback Mark the latest llama CLI/MCP result as good/bad or add a real query Write skill_correction_add Record a long-term correction rule for a persona/skill (e.g. Write wiki_restore Restore a soft-deleted wiki page (undo wiki_delete). Brings back the Write wiki_save Create or update a wiki page — Llama
READ 24 tools
Read agent_bootstrap Fetch the live Llama Command + Llama OS runtime manifest. Use this at Read auth_status Verify Llama Command credentials and return current user identity. Read brief_blocks List all brief blocks for a deal. Blocks are typed (text, link, embed, callout) Read brief_history List the content-version history of a brief block (every overwrite is snapshotted). Read deal_fact_list List a deal Read deal_fact_verify Verify a recorded fact. status= Read deal_feed The unified, time-sorted stream of every contribution to a deal — Read deal_refresh_persona Regenerate one persona Read deal_search Search the Llama Ventures deal pipeline. Fuzzy match on company name, Read deal_show Get the full canonical record for one deal by uuid. Includes status, Read html_docs_archive Archive a non- Read html_docs_list List all documents (HTML Read html_show Read the current hand-authored HTML Read html_versions List version history for a deal Read memo_show Fetch the current memo for a deal. Returns the envelope: memo Read mentions_list List @-mentions. Default scope: unresolved mentions where the caller is the Read object_inspect Explain a Llama Command URL or object id. Use for 404s, deleted wiki Read pitch_status Show the current pitch session state — session_id, started_at, idle Read skill_correction_list List the recorded corrections (long-term rules) for a persona/skill. These shape how Read skills_read Read one runtime Llama OS skill by slug. Use after skills_search. Read skills_search Search the authenticated Llama OS runtime skill library. Call this Read timeline Get the activity timeline for a deal — field changes, owner approvals, Read wiki_read Read a single wiki article from the configured Llama Command Read wiki_search Search the Llama Ventures internal wiki — deal context, company profiles,

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

Questions about Llama

Can an AI agent move money through the Llama MCP server? +

Yes. The Llama server exposes 1 financial tools including pitch_finalize. Without a policy, an autonomous agent can call these with no spend caps, no rate limits, and no approval flow. PolicyLayer lets you block financial tools by default, require human approval, or set per-tool rate limits — enforced on every call.

Can an AI agent delete data through the Llama MCP server? +

Yes. The Llama server exposes 5 destructive tools including brief_delete, html_reset, memo_reset. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Llama? +

The Llama server has 24 write tools including brief_add_callout, brief_add_link, brief_add_text. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Llama.

How many tools does the Llama MCP server expose? +

58 tools across 5 categories: Destructive, Execute, Financial, Read, Write. 24 are read-only. 34 can modify, create, or delete data.

How do I enforce a policy on Llama? +

Register the Llama MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Llama tool call.

Deterministic rules across all 58 Llama tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Instant setup, no code required.

58 Llama tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.