Low Risk

list_all_keys

Get a list of all authentication keys on the Searchcraft cluster.

How to control list_all_keys ↓

What list_all_keys does on Searchcraft MCP Server

AI agents call list_all_keys to retrieve information from Searchcraft MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why list_all_keys needs a policy

This tool retrieves and lists authentication keys, which is a read-only query operation. While exposure of key metadata could facilitate social engineering or further attacks, the tool itself only retrieves existing information without side effects. Severity is low because it returns a list (likely safe to display) rather than revealing secret key material itself, though context matters.

From the tool's definition Tool name 'list_all_keys' and description 'Get a list of all authentication keys on the Searchcraft cluster' indicate retrieval of existing data without modification, deletion, or execution of external operations.

Documented attack patterns abuse exactly the kind of access list_all_keys gives an agent:

How to control list_all_keys

PolicyLayer is an MCP gateway — it sits between your AI agents and Searchcraft MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for list_all_keys:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_all_keys": {}
  }
}

list_all_keys is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Searchcraft MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about list_all_keys

What does the list_all_keys tool do? +

Get a list of all authentication keys on the Searchcraft cluster. It is categorised as a Read tool in the Searchcraft MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_all_keys? +

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

What risk level is list_all_keys? +

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

Can I rate-limit list_all_keys? +

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

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

list_all_keys is provided by the Searchcraft MCP Server MCP server (searchcraft-inc/searchcraft-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Searchcraft MCP Server tool call.

Start from Searchcraft MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

48 Searchcraft MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.