mcp_create_project_folder_and_upload_assets
AI agents use mcp_create_project_folder_and_upload_assets 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.
The tool name 'mcp_create_project_folder_and_upload_assets' suggests it creates a folder structure and uploads files—both Write operations that modify the file system or remote storage reversibly. Without a description, confidence is reduced, but the naming convention aligns with other Write tools on this server (mcp_create_folder, mcp_create_databricks_subfolder).
From the tool's definition Tool name contains 'create' and 'upload', indicating data creation and modification operations. Description is empty, limiting certainty.
Attacks that exploit this kind of access
mcp_create_project_folder_and_upload_assets. 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_project_folder_and_upload_assets: 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_project_folder_and_upload_assets 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_project_folder_and_upload_assets 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_project_folder_and_upload_assets. 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_project_folder_and_upload_assets 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 →