secret_list

List the names of all EasyBits Secrets stored for the calling account. Values are NEVER returned — this only shows names, creation dates and last-used timestamps so you know what

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/secret-list.md

WHAT IT DOES

What secret_list does on EasyBits

AI agents call secret_list 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 secret_list is rated Low

Retrieves metadata about secrets without exposing sensitive values; no modification or execution.

From the tool's definition List the names of all EasyBits Secrets stored for the calling account. Values are NEVER returned

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs secret_list 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 secret_list, this is the rule to start with:

secret_list Allowed

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

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 secret_list call is checked against it from then on.

FAQ

Questions about secret_list

What does the secret_list tool do? +

List the names of all EasyBits Secrets stored for the calling account. Values are NEVER returned — this only shows names, creation dates and last-used timestamps so you know what. 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 secret_list? +

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

What risk level is secret_list? +

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

Can I rate-limit secret_list? +

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

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

secret_list 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 →