Low Risk

analyze_document

Analyze writing quality

How to control analyze_document ↓

AI agents call analyze_document to retrieve information from Scrivener MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Even though analyze_document only reads data, uncontrolled read access leaks sensitive information and racks up API costs — an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

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

PolicyLayer is an MCP gateway — it sits between your AI agents and Scrivener MCP Server, 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": {}
  }
}

analyze_document is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Scrivener MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the analyze_document tool do? +

Analyze writing quality. It is categorised as a Read tool in the Scrivener MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on analyze_document? +

Register the Scrivener MCP Server 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 Scrivener MCP Server. Nothing to install.

What risk level is analyze_document? +

analyze_document is a Read tool with low risk. Read-only tools are generally safe to allow by default.

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 Scrivener MCP Server MCP server (writerslogic/scrivener-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Scrivener MCP Server tool call.

Deterministic rules across all 62 Scrivener MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

62 Scrivener MCP Server tools catalogued and risk-classified — across an index of 42,500+ 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.