[PREVIEW] Add or replace field bindings on an existing visual without recreating it. mode
AI agents use pbir_bind_fields 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.
The tool modifies the field bindings of existing visuals, which is a reversible configuration change. It does not execute queries, delete data, or commit financial transactions. However, modifying visual bindings could affect report rendering and user analysis, warranting medium severity.
From the tool's definition Tool description states "Add or replace field bindings on an existing visual" — these are create/modify operations on visual configurations within Power BI reports.
Attacks that exploit this kind of access
[PREVIEW] Add or replace field bindings on an existing visual without recreating it. mode. 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.
Register the Power BI MCP Server MCP server in PolicyLayer and add a rule for pbir_bind_fields: 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.
pbir_bind_fields is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the pbir_bind_fields 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 pbir_bind_fields. 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.
pbir_bind_fields 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.