Delete a Git credential with parameter: credential_id (required)
AI agents call delete_git_credential to permanently remove resources in Databricks Permissions MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes Git credentials, which cannot be undone. Deletion of authentication credentials is a destructive operation with a significant blast radius: loss of Git access, potential service disruption, and inability to recover the credential without manual re-provisioning. While not directly financial, the impact is severe enough to classify as Destructive rather than Execute.
From the tool's definition delete_git_credential deletes a Git credential by credential_id. The verb 'delete' and the operation of removing credentials are irreversible actions.
Attacks that exploit this kind of access
Delete a Git credential with parameter: credential_id (required). It is categorised as a Destructive tool in the Databricks Permissions MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Databricks Permissions MCP Server MCP server in PolicyLayer and add a rule for delete_git_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 Permissions MCP Server. Nothing to install.
delete_git_credential is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_git_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 delete_git_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.
delete_git_credential 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 →