zitadel_list_service_user_keys

THE RISK

Low Risk

Why zitadel_list_service_user_keys needs a policy

This is a straightforward read operation that retrieves metadata about service account keys. It has no side effects, cannot modify data, and explicitly does not expose sensitive information (private keys). The blast radius of misuse is low—an attacker could enumerate existing service account keys but cannot authenticate with them or escalate privileges using metadata alone.

From the tool's definition The tool 'zitadel_list_service_user_keys' with description 'List existing keys for a service account. Shows key metadata only (not private keys).' performs a retrieval operation.

Documented attack patterns abuse exactly the kind of access zitadel_list_service_user_keys gives an agent:

POLICY

How to control zitadel_list_service_user_keys

PolicyLayer is an MCP gateway — it sits between your AI agents and Zitadel MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for zitadel_list_service_user_keys:

policy.json

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

zitadel_list_service_user_keys is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Zitadel MCP — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Zitadel MCP tools

Destructive zitadel_delete_user Permanently delete a user. This action cannot be undone. Requires confirm: true. Consider Destructive zitadel_remove_user_grant Remove a role grant from a user by grant ID. Requires confirm: true. Destructive zitadel_deactivate_user Deactivate a user account. The user will no longer be able to log in. Requires confirm: tr Write zitadel_reactivate_user Reactivate a previously deactivated user account. Write portal_register_app Register an application in the app-portal database so it appears in the portal UI. This on Write portal_setup_full_app One-click app setup: creates a Zitadel project (or uses existing), OIDC application, proje Write zitadel_create_oidc_app Create a new OIDC application in a Zitadel project. Returns the Client ID (and Client Secr Write zitadel_create_project Create a new project in Zitadel. Projects contain applications, roles, and grants.

All 26 Zitadel MCP tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about zitadel_list_service_user_keys

What does the zitadel_list_service_user_keys tool do? +

List existing keys for a service account. Shows key metadata only (not private keys). It is categorised as a Read tool in the Zitadel MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on zitadel_list_service_user_keys? +

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

What risk level is zitadel_list_service_user_keys? +

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

Can I rate-limit zitadel_list_service_user_keys? +

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

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

zitadel_list_service_user_keys is provided by the Zitadel MCP server (takleb3rry/zitadel-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Zitadel MCP tool call.

Start from Zitadel MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →