Get detailed storage credential information.
AI agents call describe_storage_credential 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.
The verb 'describe' and the action of retrieving 'detailed information' are characteristic of read-only operations. No modification, deletion, or execution of code is implied. While storage credentials are sensitive information, accessing metadata about them does not modify state or trigger external operations. This is a straightforward information retrieval with low blast radius if misused.
From the tool's definition Tool name 'describe_storage_credential' and description 'Get detailed storage credential information' indicate a retrieval operation that queries credential metadata.
Documented attack patterns abuse exactly the kind of access describe_storage_credential gives an agent:
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 describe_storage_credential:
{
"version": "1",
"default": "deny",
"tools": {
"describe_storage_credential": {}
}
} describe_storage_credential is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get detailed storage credential information. It is categorised as a Read tool in the Databricks MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Databricks MCP Server MCP server in PolicyLayer and add a rule for describe_storage_credential: 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.
describe_storage_credential is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the describe_storage_credential 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.
Set action: deny in the PolicyLayer policy for describe_storage_credential. 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.
describe_storage_credential 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.
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.