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.
69
84%
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 required runtime workflow fetches MCP tool definitions from a specified Databricks MCP endpoint (e.g., `mcp_client.get_tools()` using `url=f"{host}/api/2.0/mcp/genie/... "`), so an outsider who can author content served through that MCP interface could cause the LLM to ingest free text tool data.
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 constructs and calls MCP server endpoints at runtime (e.g., f"{host}/api/2.0/mcp/genie/01234567-89ab-cdef" and https://mcp-my-server.cloud.databricks.com/mcp) via mcp_client.get_tools(), which fetches remote tool definitions that can directly control agent prompts or execute code.
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.