Retrieves detailed information about a specific relationship between Dataverse tables, including its configuration, cascade settings, and menu behavior. Use this to inspect relationship definitions and understand table connections.
AI agents call get_dataverse_relationship to retrieve information from Dataverse 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 queries relationship metadata from Dataverse without modifying, creating, or deleting any data or configurations. It is a read-only inspection operation with minimal risk if misused by an AI agent.
From the tool's definition Tool name contains 'get' and description states 'Retrieves detailed information' with purpose to 'inspect relationship definitions.' No modification, deletion, or execution of operations occurs.
Attacks that exploit this kind of access
Retrieves detailed information about a specific relationship between Dataverse tables, including its configuration, cascade settings, and menu behavior. Use this to inspect relationship definitions and understand table connections. It is categorised as a Read tool in the Dataverse MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Dataverse MCP Server MCP server in PolicyLayer and add a rule for get_dataverse_relationship: 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 Dataverse MCP Server. Nothing to install.
get_dataverse_relationship 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_dataverse_relationship 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_dataverse_relationship. 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_dataverse_relationship is provided by the Dataverse MCP Server MCP server (wizspdemo/dataverse-mcp3). 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 →