Low Risk

list_storage_credentials

List all storage credentials configured in the workspace.

How to control list_storage_credentials ↓

What list_storage_credentials does on Databricks MCP Server

AI agents call list_storage_credentials to retrieve information from Databricks 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_storage_credentials needs a policy

This tool queries and returns a list of existing storage credentials without creating, modifying, deleting, or executing any operations. It is a passive information retrieval action. The severity is low because while exposure of credential configurations could be sensitive, the tool itself only reads metadata about credentials rather than accessing the actual credentials or external resources they protect.

From the tool's definition Tool name 'list_storage_credentials' and description 'List all storage credentials configured in the workspace' indicate a retrieval operation with no modification or execution of external effects.

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

How to control list_storage_credentials

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

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

list_storage_credentials 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 Databricks 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_storage_credentials

What does the list_storage_credentials tool do? +

List all storage credentials configured in the workspace. It is categorised as a Read tool in the Databricks MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_storage_credentials? +

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

What risk level is list_storage_credentials? +

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

Can I rate-limit list_storage_credentials? +

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

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

list_storage_credentials is provided by the Databricks MCP Server MCP server (pulkitxchadha/awesome-databricks-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Databricks MCP Server tool call.

Start from Databricks 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.

86 Databricks 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.