Create or clone a repo with parameters: url, provider, branch (optional)
AI agents use create_repo to create or update resources in Databricks MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Databricks MCP Server environment.
This tool creates or modifies workspace state by adding a new repository, which is a reversible Write operation. It does not execute arbitrary code (Execute), permanently delete data (Destructive), or move money (Financial). While repositories can contain code that might later be executed, the tool itself only performs creation/cloning.
From the tool's definition Tool name 'create_repo' and description 'Create or clone a repo' indicates creation of a new repository or cloning an existing one into the Databricks workspace.
Attacks that exploit this kind of access
Create or clone a repo with parameters: url, provider, branch (optional). It is categorised as a Write tool in the Databricks MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Databricks MCP Server MCP server in PolicyLayer and add a rule for create_repo: 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.
create_repo is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_repo 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 create_repo. 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.
create_repo is provided by the Databricks MCP Server MCP server (robkisk/databricks-mcp). 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 →