AI agents use create_notebook to create or update resources in Marimo — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Marimo environment.
This tool creates a new file artifact (a marimo notebook) which is a reversible write operation. It does not execute code, delete data, or move money. While file creation could theoretically be destructive if it overwrites an existing file at the same path, the description specifies creating 'a new' notebook, suggesting normal creation semantics.
From the tool's definition Tool description states 'Create a new marimo notebook at the given absolute path.' The verb 'Create' indicates data creation, and a notebook file is a persistent data artifact.
Attacks that exploit this kind of access
Create a new marimo notebook at the given absolute path. It is categorised as a Write tool in the Marimo MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Marimo MCP server in PolicyLayer and add a rule for create_notebook: 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 Marimo. Nothing to install.
create_notebook is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_notebook 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 create_notebook. 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.
create_notebook is provided by the Marimo MCP server (vladisluv12/marimo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
create_notebook is one line of Marimo's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →