AI agents call get_outline to retrieve information from Scrivener without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays project structure and metadata (binder organization, synopses, labels, statuses) without modifying any data. It is a read-only query operation with no side effects, placing it firmly in the Read category with low severity due to minimal blast radius if misused by an agent.
From the tool's definition Tool name 'get_outline' and description 'Returns the binder as a nested tree with synopses, labels, and statuses' indicate retrieval of hierarchical metadata. No mutation, creation, deletion, or execution is mentioned or implied.
Attacks that exploit this kind of access
Returns the binder as a nested tree with synopses, labels, and statuses — the single best tool for understanding a project. It is categorised as a Read tool in the Scrivener MCP Server, which means it retrieves data without modifying state.
Register the Scrivener MCP server in PolicyLayer and add a rule for get_outline: 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. Nothing to install.
get_outline is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_outline 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.
Set action: deny in the PolicyLayer policy for get_outline. 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.
get_outline is provided by the Scrivener MCP server (sschmitt-cg/scrivener-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →