Skip to main content
Glama
mrz1880

mcp-keycloak-admin

List authorization policies

keycloak_authz_policies_list
Read-onlyIdempotent

Retrieve the authorization policies defined on a Keycloak client. Use it to review the rules that decide access, combining with other tools for full authorization model understanding.

Instructions

Lists the authorization-services policies defined on a Keycloak client (the rules, such as role, user, or JS policies, that decide whether access is granted). Read-only and idempotent: it performs no writes and returns the same data for unchanged configuration. Use it to review the policies that back a client's permissions; call keycloak_clients_list first to obtain the client's internal id, and combine with keycloak_authz_resources_list and keycloak_authz_permissions_list to understand the whole authorization model. Returns a JSON array of policy entries, or the text "Client not found." when no client matches the given id.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
clientIdYesThe Keycloak internal id of the client whose authorization-services configuration to read. This is the UUID-style id (clientUuid), not the human-readable clientId string; obtain it from keycloak_clients_list. Required.
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Adds behavioral context beyond annotations: explicitly states read-only and idempotent nature, and mentions possible 'Client not found' return. Annotations already cover safety profile, so description adds value without contradiction.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Concise single paragraph of four sentences, each serving a purpose: purpose, behavior, usage guidance, return format. No filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Sufficiently complete given tool simplicity: describes return value (JSON array or error text), provides context for integration with sibling tools, and no output schema is needed because description covers it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Adds significant meaning beyond schema: clarifies that clientId is the UUID-style internal id (not the human-readable name) and directs to obtain it from keycloak_clients_list. Schema coverage is 100%, but description enhances understanding.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states it lists authorization policies on a Keycloak client, specifying the resource and scope. Distinct from sibling tools like keycloak_authz_resources_list and keycloak_authz_permissions_list by focusing on policies.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit guidance to first call keycloak_clients_list to get the client's internal id, and suggests combining with related authz tools. Lacks explicit when-not-to-use but context is clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mrz1880/mcp-keycloak-admin'

If you have feedback or need assistance with the MCP directory API, please join our Discord server