Get the data flow visualization for a Birst space. Shows how data sources are connected.
AI agents call birst_get_dataflow to retrieve information from Infor Birst 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 displays the data flow diagram/lineage for a Birst space. It is a read-only operation that queries metadata about how data sources are connected. No data is created, modified, deleted, or executed—it simply visualizes existing relationships.
From the tool's definition Tool name 'birst_get_dataflow' and description 'Get the data flow visualization' — uses the verb 'Get' which indicates retrieval with no modification. Shows data lineage/visualization without side effects.
Attacks that exploit this kind of access
Get the data flow visualization for a Birst space. Shows how data sources are connected. It is categorised as a Read tool in the Infor Birst MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Infor Birst MCP Server MCP server in PolicyLayer and add a rule for birst_get_dataflow: 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 Infor Birst MCP Server. Nothing to install.
birst_get_dataflow 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 birst_get_dataflow 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 birst_get_dataflow. 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.
birst_get_dataflow is provided by the Infor Birst MCP Server MCP server (mikahdev/infor-birst-mcp). 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 →