update_role · API-Central MCP: Risk & Policy

WHAT IT DOES

What update_role does on API-Central

AI agents use update_role to create or update resources in API-Central — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your API-Central environment.

WHY IT NEEDS A POLICY

Why update_role needs a policy

This tool modifies existing wireless role configurations in the Central Library through a PUT request. This is a Write operation as it creates or modifies data reversibly. Severity is medium because misconfiguration of wireless roles could impact network access controls and connectivity, but the change is reversible through subsequent updates.

From the tool's definition Tool name contains 'update' and description explicitly states 'PUT-update an existing wireless role', which is a reversible modification operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_role Rate-limited

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.

View as policy code

policy.json

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

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches API-Central, so you can run agents against it safely.

FAQ

Questions about update_role

What does the update_role tool do? +

PUT-update an existing wireless role in the Central Library. target: see create_role. It is categorised as a Write tool in the API-Central MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on update_role? +

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

What risk level is update_role? +

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

Can I rate-limit update_role? +

Yes. Add a rate_limit block to the 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 update_role completely? +

Set action: deny in the PolicyLayer policy for 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 update_role? +

update_role is provided by the API-Central MCP server (secure-ssid/centralmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.