api_key_list

List all API keys configured on the system. Shows key names and metadata (not the secret values).

SERVERTruenas SOURCEspranab/truenas-mcp

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/spranab-truenas-mcp/api-key-list.md

WHAT IT DOES

What api_key_list does on Truenas

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

RISK

Why api_key_list is rated Low

This tool performs a query/list operation that retrieves metadata about API keys without returning sensitive secret values or modifying any data. It has no side effects and poses minimal risk as it only exposes non-sensitive configuration information. The explicit mention that secret values are NOT included further confirms this is a safe read operation.

From the tool's definition Tool description explicitly states 'List all API keys configured on the system' and clarifies it shows 'key names and metadata (not the secret values)', indicating a read-only operation that retrieves information without modification.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs api_key_list safely

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

api_key_list Allowed

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

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

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

FAQ

Questions about api_key_list

What does the api_key_list tool do? +

List all API keys configured on the system. Shows key names and metadata (not the secret values). It is categorised as a Read tool in the Truenas MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on api_key_list? +

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

What risk level is api_key_list? +

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

Can I rate-limit api_key_list? +

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

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

api_key_list is provided by the Truenas MCP server (spranab/truenas-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Truenas, and thousands of servers like it.

This server

All 279 Truenas tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

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