list_api_keys

List all API keys on the account. Shows prefix, scope, and revocation status. Does NOT show raw tokens. Lists default short; pass detail=medium/full for more fields.

SERVERPostking Mcp SOURCEpostking-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/io-github-bitsandtea-postking-mcp/list-api-keys.md

WHAT IT DOES

What list_api_keys does on Postking Mcp

AI agents call list_api_keys to retrieve information from Postking Mcp 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_api_keys is rated Low

This tool retrieves and displays metadata about existing API keys but does not create, modify, delete, or expose sensitive values (raw tokens). It has no side effects and serves an informational purpose. The absence of raw token exposure further confirms this is safe read access. Blast radius is low since it only reveals non-sensitive information an authenticated user would have authorization to view.

From the tool's definition Tool name is 'list_api_keys' and description states 'List all API keys' with output limited to 'prefix, scope, and revocation status' without exposing 'raw tokens'. This is a query/listing operation with no data modification.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_api_keys safely

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

list_api_keys Allowed

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

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

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

FAQ

Questions about list_api_keys

What does the list_api_keys tool do? +

List all API keys on the account. Shows prefix, scope, and revocation status. Does NOT show raw tokens. Lists default short; pass detail=medium/full for more fields. It is categorised as a Read tool in the Postking Mcp MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_api_keys? +

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

What risk level is list_api_keys? +

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

Can I rate-limit list_api_keys? +

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

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

list_api_keys is provided by the Postking MCP server (postking-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

What list_api_keys does on Postking Mcp

Why list_api_keys is rated Low

The rule that runs list_api_keys safely

Questions about list_api_keys

More on Postking, and thousands of servers like it.