AI agents call get_report_state to retrieve information from PBIFORGE without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and returns information about the current state of a report without modifying, creating, deleting, or executing any operations. It is a pure read operation with minimal blast radius if misused by an AI agent—at worst, it could expose internal report structure details, but cannot alter systems or data.
From the tool's definition Tool name 'get_report_state' and description 'Return the current report structure for inspection' indicate retrieval/query of existing data with no modification or side effects.
Attacks that exploit this kind of access
Return the current report structure for inspection. It is categorised as a Read tool in the PBIFORGE MCP Server, which means it retrieves data without modifying state.
Register the PBIFORGE MCP server in PolicyLayer and add a rule for get_report_state: 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.
get_report_state 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 get_report_state 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 get_report_state. 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.
get_report_state 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 →