List all Git credentials
AI agents call list_git_credentials to retrieve information from Databricks Permissions MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns a list of Git credentials without modifying, deleting, or executing any operations. However, the severity is elevated to medium (rather than low) because Git credentials can be sensitive authentication tokens that could expose access to code repositories if disclosed to an unauthorized actor.
From the tool's definition Tool name is 'list_git_credentials' and description states 'List all Git credentials' — a retrieval operation with no modification or deletion.
Attacks that exploit this kind of access
List all Git credentials. It is categorised as a Read tool in the Databricks Permissions MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Databricks Permissions MCP Server MCP server in PolicyLayer and add a rule for list_git_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 Permissions MCP Server. Nothing to install.
list_git_credentials 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 list_git_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.
Set action: deny in the PolicyLayer policy for list_git_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.
list_git_credentials is provided by the Databricks Permissions MCP Server MCP server (justtryai/databricks-permissions-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →