Create a new notebook in Microsoft Fabric workspace using the official API
AI agents use create-fabric-notebook to create or update resources in Fabric-Analytics-MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Fabric-Analytics-MCP environment.
This tool creates new artifacts (notebooks) in a workspace—a reversible modification operation. It does not execute code, delete data, or move money, so it is classified as Write rather than Execute or Destructive.
From the tool's definition Tool name 'create-fabric-notebook' and description 'Create a new notebook in Microsoft Fabric workspace using the official API' explicitly indicate creation of a new resource.
Documented attack patterns abuse exactly the kind of access create-fabric-notebook gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Fabric-Analytics-MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for create-fabric-notebook:
{
"version": "1",
"default": "deny",
"tools": {
"create-fabric-notebook": {
"limits": [
{
"counter": "create-fabric-notebook_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create-fabric-notebook stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Create a new notebook in Microsoft Fabric workspace using the official API. It is categorised as a Write tool in the Fabric-Analytics-MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Fabric-Analytics- MCP server in PolicyLayer and add a rule for create-fabric-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 Fabric-Analytics-MCP. Nothing to install.
create-fabric-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-fabric-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-fabric-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-fabric-notebook is provided by the Fabric-Analytics- MCP server (santhoshravindran7/fabric-analytics-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 83 Fabric-Analytics-MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
83 Fabric-Analytics-MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.