create_allow_all_role · API-Central MCP: Risk & Policy

WHAT IT DOES

What create_allow_all_role does on API-Central

AI agents use create_allow_all_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 create_allow_all_role needs a policy

This tool creates a new security policy object (a wireless role with permit-all rules) that modifies network access controls. While creation is reversible (the role can be deleted), this is a Write operation. Severity is high because creating an overly permissive wireless role could significantly weaken network security posture and allow unauthorized access if an agent misconfigures it.

From the tool's definition Tool name 'create_allow_all_role' and description 'Create a permit-all wireless role and scope-map it' indicate creation of a network access control policy that grants unrestricted permissions.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_allow_all_role Rate-limited

create_allow_all_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": {
    "create_allow_all_role": {
      "limits": [
        {
          "counter": "create_allow_all_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 create_allow_all_role

What does the create_allow_all_role tool do? +

Create a permit-all wireless role and scope-map it. 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 create_allow_all_role? +

Register the API-Central MCP server in PolicyLayer and add a rule for create_allow_all_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 create_allow_all_role? +

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

Can I rate-limit create_allow_all_role? +

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

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

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