list_saved_keys

List your saved keys & secrets (Profile → API KEYS) — each with its provider, its ALIAS (the name a harness attaches it by via secret_refs), and a MASKED preview. NEVER returns a value. Covers pasted API keys, custom secrets, and OAuth-brokered grants. Requires a logged-in identity.

SERVERRokha SOURCEhttps://rokha.ai/mcp/jsonrpc

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/ai-rokha-rokha/list-saved-keys.md

WHAT IT DOES

What list_saved_keys does on Rokha

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

RISK

Why list_saved_keys is rated Low

Retrieves sensitive credential metadata; no side effects but enables reconnaissance of security posture.

From the tool's definition List your saved keys & secrets, MASKED preview, NEVER returns a value

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_saved_keys safely

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

list_saved_keys Allowed

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

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

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

FAQ

Questions about list_saved_keys

What does the list_saved_keys tool do? +

How do I enforce a policy on list_saved_keys? +

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

What risk level is list_saved_keys? +

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

Can I rate-limit list_saved_keys? +

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

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

list_saved_keys is provided by the Rokha MCP server (https://rokha.ai/mcp/jsonrpc). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Rokha, and thousands of servers like it.

This server

All 216 Rokha tools →

Across the catalogue

list_symbols on ACE-MCP →aiva_list_affiliates on AIVA MCP Server → The MCP Attack Database →

Guides

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