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.
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.
This tool creates new organizational structures (solutions) in Dataverse that persist and can be deployed across environments. While reversible (solutions can be deleted), it has high blast radius because unintended solution creation could lead to deployment conflicts, confusion in enterprise solution management, and potential overwriting of custom components across connected environments.
From the tool's definition Tool description explicitly states 'Creates a new unmanaged solution in Dataverse' and describes solutions as containers for customizations that can be packaged and deployed. This is a create operation that modifies the Dataverse schema.
Documented attack patterns abuse exactly the kind of access create_dataverse_solution gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Dataverse MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for create_dataverse_solution:
{
"version": "1",
"default": "deny",
"tools": {
"create_dataverse_solution": {
"limits": [
{
"counter": "create_dataverse_solution_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}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.
Free to start. No card required.
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.
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.
create_dataverse_solution is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
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.
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.
create_dataverse_solution is provided by the Dataverse MCP Server MCP server (mwhesse/dataverse-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Dataverse MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
71 Dataverse MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.