Update an existing item in Microsoft Fabric workspace
AI agents use update-fabric-item 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.
The tool creates or modifies data (an existing item) in a reversible manner, fitting the Write category. Severity is high because updating items in a data analytics workspace could affect downstream analyses, reports, and business decisions that depend on that data, creating significant blast radius if misused by an AI agent (e.g., corrupting notebooks, dataflows, or datasets).
From the tool's definition Tool name includes 'update' and description states 'Update an existing item in Microsoft Fabric workspace' — this modifies data reversibly within a workspace.
Documented attack patterns abuse exactly the kind of access update-fabric-item 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 update-fabric-item:
{
"version": "1",
"default": "deny",
"tools": {
"update-fabric-item": {
"limits": [
{
"counter": "update-fabric-item_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}update-fabric-item 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.
Update an existing item in Microsoft Fabric workspace. 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 update-fabric-item: 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.
update-fabric-item 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 update-fabric-item 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 update-fabric-item. 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.
update-fabric-item 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.