list_ai_keys

List your configured AI provider API keys (values are masked)

SERVEREasyBits SOURCE@easybits.cloud/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/cloud-easybits-easybits/list-ai-keys.md

WHAT IT DOES

What list_ai_keys does on EasyBits

AI agents call list_ai_keys to retrieve information from EasyBits 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_ai_keys is rated Low

Retrieves sensitive credential metadata; masked values limit immediate exposure but reveal which API providers are configured.

From the tool's definition List your configured AI provider API keys (values are masked)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_ai_keys safely

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

list_ai_keys Allowed

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

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

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

FAQ

Questions about list_ai_keys

What does the list_ai_keys tool do? +

List your configured AI provider API keys (values are masked). It is categorised as a Read tool in the EasyBits MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_ai_keys? +

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

What risk level is list_ai_keys? +

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

Can I rate-limit list_ai_keys? +

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

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

list_ai_keys is provided by the EasyBits MCP server (@easybits.cloud/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on EasyBits, and thousands of servers like it.

This server

All 273 EasyBits 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 →