pbip_fix_broken_visuals

Fix broken visual references after a table rename. Use this when TOM/API renamed a table but visuals still reference the old name. Supports both PBIR-Legacy and PBIR-Enhanced formats.

Server Power BI MCP Server sulaiman013/powerbi-mcp
Category Write
Risk class Medium
Parameters 00 required

What pbip_fix_broken_visuals does on Power BI MCP Server

AI agents use pbip_fix_broken_visuals to create or update resources in Power BI MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Power BI MCP Server environment.

Why pbip_fix_broken_visuals needs a policy

This tool modifies Power BI report files by updating visual references to point to renamed tables. It rewrites existing visual definitions, which is a reversible write operation (the old references are replaced with new ones). However, the blast radius is high because incorrect fixes could break multiple visuals across reports, potentially corrupting the report layout or rendering for end users.

From the tool's definition Fix broken visual references after a table rename... Supports both PBIR-Legacy and PBIR-Enhanced formats

Questions about pbip_fix_broken_visuals

What does the pbip_fix_broken_visuals tool do? +

Fix broken visual references after a table rename. Use this when TOM/API renamed a table but visuals still reference the old name. Supports both PBIR-Legacy and PBIR-Enhanced formats. It is categorised as a Write tool in the Power BI MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on pbip_fix_broken_visuals? +

Register the Power BI MCP Server MCP server in PolicyLayer and add a rule for pbip_fix_broken_visuals: 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.

What risk level is pbip_fix_broken_visuals? +

pbip_fix_broken_visuals is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit pbip_fix_broken_visuals? +

Yes. Add a rate_limit block to the pbip_fix_broken_visuals 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.

How do I block pbip_fix_broken_visuals completely? +

Set action: deny in the PolicyLayer policy for pbip_fix_broken_visuals. 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.

What MCP server provides pbip_fix_broken_visuals? +

pbip_fix_broken_visuals 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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.