Update properties of a security role (name, description, business unit). At least one field must be provided.
AI agents use update-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 or modifies data reversibly by updating security role properties. While security roles are sensitive (affecting access control), the operation is not destructive (roles are not deleted), not financial, and not code execution.
From the tool's definition Tool name 'update-security-role' and description states it 'Update properties of a security role (name, description, business unit)'. The action modifies existing security role metadata fields.
Documented attack patterns abuse exactly the kind of access update-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 update-security-role:
{
"version": "1",
"default": "deny",
"tools": {
"update-security-role": {
"limits": [
{
"counter": "update-security-role_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}update-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.
Update properties of a security role (name, description, business unit). At least one field must be provided. 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 update-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.
update-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 update-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 update-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.
update-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.