list_database_principals
AI agents call list_database_principals to retrieve information from Fabric Dw Mcp Cli 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 database principals without modifying data. While the description is empty (lowering confidence slightly), the name clearly indicates a listing/read operation. Even if principals could theoretically be enumerated for reconnaissance, the actual listing action itself is non-destructive and non-manipulative. No code execution, data modification, or deletion occurs.
From the tool's definition Tool name 'list_database_principals' indicates a read operation that retrieves a list of principals (users/roles) from a database. The name pattern 'list_*' is a standard read operation.
Attacks that exploit this kind of access
list_database_principals. It is categorised as a Read tool in the Fabric Dw Mcp Cli MCP Server, which means it retrieves data without modifying state.
Register the Fabric Dw Mcp Cli MCP server in PolicyLayer and add a rule for list_database_principals: 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 Dw Mcp Cli. Nothing to install.
list_database_principals 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 list_database_principals 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 list_database_principals. 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.
list_database_principals is provided by the Fabric Dw Mcp Cli MCP server (sdebruyn/fabric-dw-mcp-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →