create_dataverse_relationship · Dataverse MCP Server MCP

WHAT IT DOES

What create_dataverse_relationship does on Dataverse MCP Server

AI agents use create_dataverse_relationship to create or update resources in Dataverse MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Dataverse MCP Server environment.

WHY IT NEEDS A POLICY

Why create_dataverse_relationship needs a policy

This tool creates schema relationships (One-to-Many, Many-to-Many) between tables. Schema modifications are Write operations (create/modify data reversibly). While consequential for data integrity and application logic, relationship creation is not destructive (relationships can be removed) nor does it execute arbitrary code or move financial data.

From the tool's definition Tool name and description both indicate 'Creates a relationship between two Dataverse tables' - a data creation operation that modifies schema structure.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_dataverse_relationship Rate-limited

create_dataverse_relationship stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_dataverse_relationship": {
      "limits": [
        {
          "counter": "create_dataverse_relationship_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Dataverse MCP Server, so you can run agents against it safely.

FAQ

Questions about create_dataverse_relationship

What does the create_dataverse_relationship tool do? +

Creates a relationship between two Dataverse tables. Supports One-to-Many relationships (parent-child with lookup field) and Many-to-Many relationships (junction table). Use this to establish data connections between tables, enable navigation, and maintain referential integrity. It is categorised as a Write tool in the Dataverse MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create_dataverse_relationship? +

Register the Dataverse MCP Server MCP server in PolicyLayer and add a rule for create_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.

What risk level is create_dataverse_relationship? +

create_dataverse_relationship is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit create_dataverse_relationship? +

Yes. Add a rate_limit block to the create_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.

How do I block create_dataverse_relationship completely? +

Set action: deny in the PolicyLayer policy for create_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.

What MCP server provides create_dataverse_relationship? +

create_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.