clearpass_list_roles

List ClearPass roles with bounded pagination.

SERVERAPI-Central SOURCEsecure-ssid/centralmcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/secure-ssid-centralmcp/clearpass-list-roles.md

WHAT IT DOES

What clearpass_list_roles does on API-Central

AI agents call clearpass_list_roles to retrieve information from API-Central without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why clearpass_list_roles is rated Low

This is a straightforward listing/querying operation that retrieves role information from ClearPass. It has no side effects, creates no resources, executes no commands, and makes no destructive or financial changes. The bounded pagination indicates it is a safe, read-only retrieval of configuration metadata.

From the tool's definition Tool name 'clearpass_list_roles' and description 'List ClearPass roles with bounded pagination' indicate a retrieval operation that queries and returns existing role data without modification.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs clearpass_list_roles safely

PolicyLayer is an MCP gateway: it sits between your AI agents and API-Central, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For clearpass_list_roles, this is the rule to start with:

clearpass_list_roles Allowed

clearpass_list_roles is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "clearpass_list_roles": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect API-Central, apply this rule, and every clearpass_list_roles call is checked against it from then on.

FAQ

Questions about clearpass_list_roles

What does the clearpass_list_roles tool do? +

List ClearPass roles with bounded pagination. It is categorised as a Read tool in the API-Central MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on clearpass_list_roles? +

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

clearpass_list_roles is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit clearpass_list_roles? +

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

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

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

KEEP EXPLORING

More on API-Central, and thousands of servers like it.

This server

All 590 API-Central tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →