mcp_create_folder
AI agents use mcp_create_folder 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.
Creating a folder is a reversible modification operation (folders can be deleted). It has minimal blast radius—an AI agent misusing this tool would create unwanted directories, which is easily remediated. This falls under Write rather than Execute or Destructive. Confidence is moderate (0.75) due to the empty description, but the tool name and sibling context provide sufficient evidence.
From the tool's definition Tool name 'mcp_create_folder' indicates creation of a folder/directory. Description is empty, but sibling tools like 'mcp_create_databricks_subfolder', 'mcp_create_databricks_user_folder', and 'mcp_create_project_folder_and_upload_assets' confirm this server…
Attacks that exploit this kind of access
mcp_create_folder. 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 mcp_create_folder: 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.
mcp_create_folder 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 mcp_create_folder 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 mcp_create_folder. 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.
mcp_create_folder is provided by the Databricks MCP Server MCP server (stephenjhsu/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 →