Append privileges to a security role using AddPrivilegesRole. Existing privileges are preserved.
AI agents use add-security-role-privileges 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 modifies security role configuration by appending privileges. While the description states 'existing privileges are preserved', the operation creates new privilege assignments in the security model. This is a Write operation (reversible modification) rather than Destructive because privileges can be removed and roles can be reconfigured.
From the tool's definition Tool appends privileges to a security role using 'AddPrivilegesRole'. It modifies access control metadata by adding privileges to an existing security role, which is a reversible data modification operation.
Documented attack patterns abuse exactly the kind of access add-security-role-privileges 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 add-security-role-privileges:
{
"version": "1",
"default": "deny",
"tools": {
"add-security-role-privileges": {
"limits": [
{
"counter": "add-security-role-privileges_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} add-security-role-privileges 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.
Append privileges to a security role using AddPrivilegesRole. Existing privileges are preserved. 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 add-security-role-privileges: 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.
add-security-role-privileges 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 add-security-role-privileges 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 add-security-role-privileges. 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.
add-security-role-privileges 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.