Assign a workspace to a dedicated Fabric capacity
AI agents use fabric_assign_workspace_to_capacity 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 or modifies a workspace-to-capacity assignment, which is a reversible configuration change in Microsoft Fabric. While it doesn't delete data, it has significant operational impact (affects resource allocation and billing). It falls under Write rather than Execute because it performs a specific configuration assignment rather than arbitrary code execution.
From the tool's definition Tool name 'fabric_assign_workspace_to_capacity' and description 'Assign a workspace to a dedicated Fabric capacity' indicate a modification operation that changes workspace resource allocation configuration.
Documented attack patterns abuse exactly the kind of access fabric_assign_workspace_to_capacity 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 fabric_assign_workspace_to_capacity:
{
"version": "1",
"default": "deny",
"tools": {
"fabric_assign_workspace_to_capacity": {
"limits": [
{
"counter": "fabric_assign_workspace_to_capacity_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}fabric_assign_workspace_to_capacity 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.
Assign a workspace to a dedicated Fabric capacity. 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 fabric_assign_workspace_to_capacity: 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.
fabric_assign_workspace_to_capacity 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 fabric_assign_workspace_to_capacity 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 fabric_assign_workspace_to_capacity. 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.
fabric_assign_workspace_to_capacity 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.