AI agents use export_pbix to create or update resources in PBIFORGE — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your PBIFORGE environment.
The tool creates and outputs a new file artifact (a Power BI .pbix file encoded as base64). This is a Write operation—it produces persistent output data that can be saved to disk or transmitted. It is not Destructive because it does not delete or irreversibly remove existing data.
From the tool's definition Tool description states 'Compile the current session into a .pbix file and return it as base64.' This generates and exports a file artifact (a compiled .pbix Power BI file) from the current session state.
Attacks that exploit this kind of access
Compile the current session into a .pbix file and return it as base64. It is categorised as a Write tool in the PBIFORGE MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the PBIFORGE MCP server in PolicyLayer and add a rule for export_pbix: 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 PBIFORGE. Nothing to install.
export_pbix 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 export_pbix 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 export_pbix. 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.
export_pbix is provided by the PBIFORGE MCP server (twilize5/reportforge). 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 →