AI agents call remnote_get_playbook to retrieve information from Remnote without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves a static or semi-static playbook document to guide MCP agent behavior. It performs no mutations, deletions, or external operations. The outputs are reference information and decision frameworks, not modifications to RemNote data. Blast radius is negligible—misuse would at worst provide incorrect guidance, not corrupt data or trigger unintended actions.
From the tool's definition Tool name 'remnote_get_playbook' and description 'Get an operations playbook' indicate data retrieval. The description lists only informational outputs: 'status-first recommendation, navigation presets, content-mode guidance, and write-safety decision…
Attacks that exploit this kind of access
Get an operations playbook for MCP agents: status-first recommendation, navigation presets, content-mode guidance, and write-safety decision tree. It is categorised as a Read tool in the Remnote MCP Server, which means it retrieves data without modifying state.
Register the Remnote MCP server in PolicyLayer and add a rule for remnote_get_playbook: 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 Remnote. Nothing to install.
remnote_get_playbook 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 remnote_get_playbook 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 remnote_get_playbook. 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.
remnote_get_playbook is provided by the Remnote MCP server (remnote-mcp-server). 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 →