create_dataverse_solution · Dataverse MCP Server MCP

WHAT IT DOES

What create_dataverse_solution does on Dataverse MCP Server

AI agents use create_dataverse_solution 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_solution needs a policy

This tool creates a new solution object in Dataverse, which is a reversible write operation. While solutions are important infrastructure containers, creating one does not execute arbitrary code, delete data, or commit financial transactions. The blast radius is limited to adding a new customization container that can be deleted or modified later.

From the tool's definition Creates a new unmanaged solution in Dataverse. Solutions are containers for customizations and allow you to package, deploy, and manage custom components.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_dataverse_solution Rate-limited

create_dataverse_solution 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_solution": {
      "limits": [
        {
          "counter": "create_dataverse_solution_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_solution

What does the create_dataverse_solution tool do? +

Creates a new unmanaged solution in Dataverse. Solutions are containers for customizations and allow you to package, deploy, and manage custom components. Use this to create a solution before adding tables, columns, and other customizations. 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_solution? +

Register the Dataverse MCP Server MCP server in PolicyLayer and add a rule for create_dataverse_solution: 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_solution? +

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

Can I rate-limit create_dataverse_solution? +

Yes. Add a rate_limit block to the create_dataverse_solution 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_solution completely? +

Set action: deny in the PolicyLayer policy for create_dataverse_solution. 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_solution? +

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