Execute a notebook in Microsoft Fabric workspace
AI agents invoke execute-fabric-notebook to trigger actions in Fabric-Analytics-MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool triggers execution of code within a notebook environment. The effects are contingent on what the notebook contains—it could perform data transformations, trigger jobs, modify workspace state, or interact with external systems. This makes it Execute category rather than Write (which would be reversible data modification).
From the tool's definition Tool name contains 'execute' and description states it 'Execute[s] a notebook in Microsoft Fabric workspace'.
Documented attack patterns abuse exactly the kind of access execute-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 execute-fabric-notebook:
{
"version": "1",
"default": "deny",
"tools": {
"execute-fabric-notebook": {
"limits": [
{
"counter": "execute-fabric-notebook_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}execute-fabric-notebook stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Execute a notebook in Microsoft Fabric workspace. It is categorised as a Execute tool in the Fabric-Analytics-MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Fabric-Analytics- MCP server in PolicyLayer and add a rule for execute-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.
execute-fabric-notebook is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the execute-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 execute-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.
execute-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.