Create a new security role. If businessUnitId is omitted, the role is created in the root business unit. Pass solutionUniqueName to add it to a specific unmanaged solution in one step.
AI agents use create-security-role to create or update resources in PowerPlatform MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your PowerPlatform MCP environment.
This tool creates new security roles in PowerPlatform/Dataverse, which modifies the authorization structure of the system. While creational rather than destructive, security role creation has significant blast radius: a malicious agent could create roles with excessive privileges, grant those roles to compromised accounts, or disable legitimate access controls.
From the tool's definition Creates a new security role with customizable businessUnitId and solutionUniqueName parameters. The description explicitly states 'Create a new security role' which is a data creation action that persists in the system.
Risk signalsAdmin/system-level operation
Documented attack patterns abuse exactly the kind of access create-security-role gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and PowerPlatform MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for create-security-role:
{
"version": "1",
"default": "deny",
"tools": {
"create-security-role": {
"limits": [
{
"counter": "create-security-role_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create-security-role 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.
Create a new security role. If businessUnitId is omitted, the role is created in the root business unit. Pass solutionUniqueName to add it to a specific unmanaged solution in one step. It is categorised as a Write tool in the PowerPlatform MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the PowerPlatform MCP server in PolicyLayer and add a rule for create-security-role: 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 PowerPlatform MCP. Nothing to install.
create-security-role 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-security-role 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-security-role. 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-security-role is provided by the PowerPlatform MCP server (michsob/powerplatform-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from PowerPlatform MCP, 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.
66 PowerPlatform MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.