Audit where BPA rules live for the loaded PBIP project: rules embedded in the model (BestPracticeAnalyzer annotation), external rule-file URLs, and ignored rule IDs, merged with any local user/machine BPARules.json found. Reveals shadow governance and ignored rules.
AI agents call bpa_audit_rule_sources to retrieve information from Power BI 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 reports on the configuration state of BPA rules across multiple sources (model, external URLs, ignored list, local filesystem). It has no side effects: it does not create, modify, delete, or execute code. The 'reveals shadow governance' language indicates discovery/analysis, not action. Severity is low because misuse would only expose configuration details, not compromise data or systems.
From the tool's definition The tool description uses audit language: 'Audit where BPA rules live', 'Reveals shadow governance' — pure inspection/querying activities.
Attacks that exploit this kind of access
Audit where BPA rules live for the loaded PBIP project: rules embedded in the model (BestPracticeAnalyzer annotation), external rule-file URLs, and ignored rule IDs, merged with any local user/machine BPARules.json found. Reveals shadow governance and ignored rules. It is categorised as a Read tool in the Power BI MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Power BI MCP Server MCP server in PolicyLayer and add a rule for bpa_audit_rule_sources: 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 Power BI MCP Server. Nothing to install.
bpa_audit_rule_sources 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 bpa_audit_rule_sources 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 bpa_audit_rule_sources. 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.
bpa_audit_rule_sources is provided by the Power BI MCP Server MCP server (sulaiman013/powerbi-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.