List all Fabric workspaces you have access to with their IDs, types, and capacity assignments.
AI agents call workspace_list to retrieve information from Force Fabric MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves metadata about Fabric workspaces (IDs, types, capacity assignments) accessible to the user. It is a read-only query operation with no side effects, reversible operations, code execution, data destruction, or financial impact. The severity is low because workspace enumeration is informational and does not directly compromise data or systems, though it could inform further reconnaissance.
From the tool's definition Tool name 'workspace_list' and description 'List all Fabric workspaces' indicate a retrieval operation that queries and returns data without modifying, deleting, or executing operations.
Documented attack patterns abuse exactly the kind of access workspace_list gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Force Fabric MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for workspace_list:
{
"version": "1",
"default": "deny",
"tools": {
"workspace_list": {}
}
}workspace_list is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List all Fabric workspaces you have access to with their IDs, types, and capacity assignments. It is categorised as a Read tool in the Force Fabric MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Force Fabric MCP Server MCP server in PolicyLayer and add a rule for workspace_list: 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 Force Fabric MCP Server. Nothing to install.
workspace_list is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the workspace_list 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 workspace_list. 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.
workspace_list is provided by the Force Fabric MCP Server MCP server (tmdaidevs/force-fabric-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Force Fabric MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
33 Force Fabric MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.