Add tools to your agent and grant required permissions in databricks.yml. Use when: (1) Adding MCP servers, Genie spaces, vector search, or UC functions to agent, (2) Permission errors at runtime, (3) User says 'add tool', 'connect to', 'grant permission', (4) Configuring databricks.yml resources.
72
87%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Low
Low-risk findings worth noting
Low
Low-risk findings.
2 low severity findings. Worth noting, but not necessarily harmful.
The skill exposes the agent to untrusted, user-generated content from public third-party sources, creating a risk of indirect prompt injection. This includes browsing arbitrary URLs, reading social media posts or forum comments, and analyzing content from unknown websites.
The workflow’s runtime path retrieves MCP tools from a Databricks MCP server endpoint (e.g., `mcp_client.get_tools()` against `/api/2.0/mcp/genie/...`), meaning outsider-authored text could be ingested via the MCP server’s tool outputs without the agent selecting a specific item first.
The skill fetches instructions or code from an external URL at runtime, and the fetched content directly controls the agent’s prompts or executes code. This dynamic dependency allows the external source to modify the agent’s behavior without any changes to the skill itself.
The skill fetches tool definitions at runtime from MCP endpoints (e.g., f"{host}/api/2.0/mcp/genie/01234567-89ab-cdef" and https://mcp-my-server.cloud.databricks.com/mcp), which are used by mcp_client.get_tools() to inject remote tool metadata that directly controls agent behavior/instructions.
fdc1b49
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.