Create a new notebook in Fabric workspace
AI agents use create_notebook to create or update resources in Microsoft Fabric MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Microsoft Fabric MCP Server environment.
Creating a notebook is a Write operation: it creates a new persistent resource (artifact) in a workspace. Severity is high because notebooks can contain and execute arbitrary code (Python, Scala, SQL) within Fabric, so an AI agent tricked into creating a malicious notebook could enable subsequent code execution attacks.
From the tool's definition Tool description states 'Create a new notebook in Fabric workspace' — a create operation that modifies workspace state by adding a new artifact.
Attacks that exploit this kind of access
Create a new notebook in Fabric workspace. It is categorised as a Write tool in the Microsoft Fabric MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Microsoft Fabric MCP Server 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 Microsoft Fabric MCP Server. 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 Microsoft Fabric MCP Server MCP server (snahrup/microsoft-fabric-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 →