brief_restore_version · Llama MCP: Risk & Policy

WHAT IT DOES

What brief_restore_version does on Llama

AI agents use brief_restore_version to create or update resources in Llama — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Llama environment.

WHY IT NEEDS A POLICY

Why brief_restore_version needs a policy

This tool modifies existing data by reverting brief blocks to previous versions. While it restores rather than deletes, it still constitutes a write operation that changes the current state of the data. It is reversible (the current state can be restored in turn), so it does not qualify as Destructive.

From the tool's definition Tool description states 'Restore a brief block to a specific historical version', which is a modification operation that reverts data to a previous state. The tool name contains 'restore', indicating a write-type action on existing data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

brief_restore_version Rate-limited

brief_restore_version stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "brief_restore_version": {
      "limits": [
        {
          "counter": "brief_restore_version_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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 brief_restore_version

What does the brief_restore_version tool do? +

Restore a brief block to a specific historical version (find historyId via brief_history). It is categorised as a Write tool in the Llama MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on brief_restore_version? +

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

brief_restore_version is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit brief_restore_version? +

Yes. Add a rate_limit block to the brief_restore_version 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 brief_restore_version completely? +

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

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