check_keycloak

Check Keycloak identity server health via GET /health/live and /health/ready (Keycloak 20+). Falls back to /auth/health for older versions. Returns live and ready states.

SERVERMcp Nettools SOURCEaaronckj/mcp-nettools

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/aaronckj-mcp-nettools/check-keycloak.md

WHAT IT DOES

What check_keycloak does on Mcp Nettools

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

RISK

Why check_keycloak is rated Low

This is a read operation that retrieves health status from a Keycloak identity server. It does not modify, delete, or execute arbitrary code. However, severity is elevated to medium because Keycloak is a critical authentication/authorization system; health check results could inform reconnaissance or DoS attacks, and an attacker probing multiple identity servers could map infrastructure.

From the tool's definition Tool performs health checks via GET requests to /health/live, /health/ready, and /auth/health endpoints. No data modification, deletion, or financial operations are performed. The tool 'returns live and ready states' as read-only status information.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs check_keycloak safely

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

check_keycloak Allowed

check_keycloak 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": {
    "check_keycloak": {}
  }
}

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

The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Nettools, apply this rule, and every check_keycloak call is checked against it from then on.

FAQ

Questions about check_keycloak

What does the check_keycloak tool do? +

Check Keycloak identity server health via GET /health/live and /health/ready (Keycloak 20+). Falls back to /auth/health for older versions. Returns live and ready states. It is categorised as a Read tool in the Mcp Nettools MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on check_keycloak? +

Register the Mcp Nettools MCP server in PolicyLayer and add a rule for check_keycloak: 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 Nettools. Nothing to install.

What risk level is check_keycloak? +

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

Can I rate-limit check_keycloak? +

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

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

check_keycloak is provided by the Mcp Nettools MCP server (aaronckj/mcp-nettools). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Mcp Nettools, and thousands of servers like it.

This server

All 235 Mcp Nettools tools →

Across the catalogue

The MCP Attack Database →

Guides

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