List all warehouses in a Fabric workspace with their metadata and connection details.
AI agents call warehouse_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 and enumerates warehouse resources and their associated metadata without performing any side effects, modifications, or deletions. It is clearly a Read operation. However, since it returns 'connection details,' there is a risk that exposed credentials or connection strings could be misused if disclosed to an attacker, justifying medium severity rather than low.
From the tool's definition Tool description states 'List all warehouses in a Fabric workspace with their metadata and connection details.' The verb 'list' indicates a retrieval operation with no modification or deletion of data.
Documented attack patterns abuse exactly the kind of access warehouse_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 warehouse_list:
{
"version": "1",
"default": "deny",
"tools": {
"warehouse_list": {}
}
} warehouse_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 warehouses in a Fabric workspace with their metadata and connection details. 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 warehouse_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.
warehouse_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 warehouse_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 warehouse_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.
warehouse_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.