get_relationships
AI agents call get_relationships to retrieve information from PBIXRay MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'get_relationships' tool retrieves relationship information from Power BI data models, returning metadata about table relationships without modification or execution. While the description is empty, the naming convention and position among other read-only metadata tools (get_dax_tables, get_dax_columns, get_metadata) strongly suggests this is a simple query operation.
From the tool's definition Tool name 'get_relationships' follows a retrieval pattern (get_*) consistent with sibling tools like get_dax_measures, get_dax_tables, and get_metadata. These are all data-querying operations within Power BI models.
Attacks that exploit this kind of access
get_relationships. It is categorised as a Read tool in the PBIXRay MCP Server MCP Server, which means it retrieves data without modifying state.
Register the PBIXRay MCP Server MCP server in PolicyLayer and add a rule for get_relationships: 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 PBIXRay MCP Server. Nothing to install.
get_relationships 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_relationships 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_relationships. 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_relationships is provided by the PBIXRay MCP Server MCP server (ngoc0610/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 →