analyze_document

THE RISK

High Risk

This tool executes an analysis operation using an RLM engine on a document, which involves running a computational process (the Lattice/Nucleus DSL engine) against input data. It goes beyond simple retrieval — it triggers external computation.

From the tool's definition Analyze a document using the Recursive Language Model (RLM)

Documented attack patterns abuse exactly the kind of access analyze_document gives an agent:

HOW TO CONTROL ANALYZE_DOCUMENT

PolicyLayer is an MCP gateway — it sits between your AI agents and Lattice, and nothing reaches the server without passing your rules. This is the rule we recommend for analyze_document:

policy.json

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

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

Create a free account and register Lattice — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

More Lattice tools

Destructive lattice_memo_delete Delete a memo that is no longer needed to free memory. Use this when context becomes stal Destructive lattice_reset Clear all handles and bindings but keep the document loaded. Use this to start fresh analy Execute nucleus_execute Execute Nucleus commands directly on a document without LLM orchestration. Execute lattice_llm_batch_respond Resolve a pending (llm_batch …) suspension with all N responses at once. (llm_batch COLL Execute lattice_llm_respond Resolve a pending (llm_query …) suspension with a single string response. When lattice_qu Execute lattice_query Execute a Nucleus query on the loaded document. Write lattice_close Close the current session and free memory. Read lattice_bindings Show current handle bindings. Returns all active handles with their stubs: $grep_error:

All 15 Lattice tools →

Execute tools on other servers

Frida Game Hacking MCP remove_breakpoint Procmon request_elevation WireMCP capture_packets Pentest Ai run_probe

Go deeper

High-risk tools in Lattice → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

What does the analyze_document tool do? +

Analyze a document using the Recursive Language Model (RLM). It is categorised as a Execute tool in the Lattice MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on analyze_document? +

Register the Lattice MCP server in PolicyLayer and add a rule for analyze_document: 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 Lattice. Nothing to install.

What risk level is analyze_document? +

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

Can I rate-limit analyze_document? +

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

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

analyze_document is provided by the Lattice MCP server (yogthos/matryoshka). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Lattice tool call.

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

GOVERN LATTICE →

Free to start. No card required.

15 Lattice tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// WHAT ANALYZE_DOCUMENT ON LATTICE DOES

// THE RISK

// HOW TO CONTROL ANALYZE_DOCUMENT

// EXPLORE