create_or_update_role

THE RISK

Medium Risk

Why create_or_update_role needs a policy

This tool modifies user roles within the Coroot platform, which affects access control and permissions. While the changes are reversible (roles can be updated again or recreated), the high severity reflects the security implications of role management—unauthorized role changes could grant or revoke access to sensitive observability data and infrastructure controls.

From the tool's definition Tool name explicitly states 'create_or_update' which indicates reversible modification of data. Description specifies 'Create or update a user role' with admin-only access restriction.

Risk signalsAdmin/system-level operation

Documented attack patterns abuse exactly the kind of access create_or_update_role gives an agent:

POLICY

How to control create_or_update_role

PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Server for Coroot, and nothing reaches the server without passing your rules. This is the rule we recommend for create_or_update_role:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_or_update_role": {
      "limits": [
        {
          "counter": "create_or_update_role_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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

Create a free account and register MCP Server for Coroot — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More MCP Server for Coroot tools

Destructive delete_api_key Delete an API key. Destructive delete_application_category Delete an application category. Destructive delete_custom_cloud_pricing Delete custom cloud pricing configuration. Destructive delete_dashboard Delete a custom dashboard. Destructive delete_integration Delete an integration configuration. Destructive delete_project Delete a project and all associated data. Execute test_integration Test an integration configuration. Write configure_integration configure_integration

All 61 MCP Server for Coroot tools →

Write tools on other servers

M-Team MCP Server download_torrent YouTube MCP Server generate_video_title Android Forensics ADB MCP Server combine_reports 0xarchive web3_signup

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Argument validation → Checking tool call arguments against schema and policy before they run.
Scoped token → Per-person credentials that grant a defined subset of servers and tools.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about create_or_update_role

What does the create_or_update_role tool do? +

Create or update a user role (admin only). It is categorised as a Write tool in the MCP Server for Coroot 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_or_update_role? +

Register the MCP Server for Coroot MCP server in PolicyLayer and add a rule for create_or_update_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 MCP Server for Coroot. Nothing to install.

What risk level is create_or_update_role? +

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

Can I rate-limit create_or_update_role? +

Yes. Add a rate_limit block to the create_or_update_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.

How do I block create_or_update_role completely? +

Set action: deny in the PolicyLayer policy for create_or_update_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.

What MCP server provides create_or_update_role? +

create_or_update_role is provided by the MCP Server for Coroot MCP server (jamesbrink/mcp-coroot). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every MCP Server for Coroot tool call.

Start from MCP Server for Coroot, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →