clearpass_disconnect_session
Disconnect an active ClearPass session via Change of Authorization.
This record as markdown: /tools/secure-ssid-centralmcp/clearpass-disconnect-session.md
What clearpass_disconnect_session does on API-Central
AI agents invoke clearpass_disconnect_session to trigger actions in API-Central. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why clearpass_disconnect_session is rated High
This tool triggers an external network operation (Change of Authorization / CoA) that forcibly terminates an active user session on the ClearPass policy server. It executes a real-time network control action with immediate effect on connected users.
From the tool's definition Disconnect an active ClearPass session via Change of Authorization
Attacks that exploit this kind of access
The rule that runs clearpass_disconnect_session 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_disconnect_session, this is the rule to start with:
clearpass_disconnect_session stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect API-Central, apply this rule, and every clearpass_disconnect_session call is checked against it from then on.
Questions about clearpass_disconnect_session
Disconnect an active ClearPass session via Change of Authorization. It is categorised as a Execute tool in the API-Central MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the API-Central MCP server in PolicyLayer and add a rule for clearpass_disconnect_session: 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.
clearpass_disconnect_session is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the clearpass_disconnect_session 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 clearpass_disconnect_session. 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.
clearpass_disconnect_session 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.
More on API-Central, and thousands of servers like it.
Across the catalogue