tools.list field of an agent YAML (the standalone agent runtime that powers Slack Bot, Programmable, and Bolt Pipeline agents). Use allowlist mode to restrict an agent to only what it needs, or denylist to remove tools from the default set. See YAML Configuration for syntax.
No
tools block = full tool access. Side-effectful tools (for example trigger_bolt_schedule_run and the Bolt retries) are never available unless named explicitly in an allowlist. Overriding a schedule’s commands or branch is a separate tool, trigger_bolt_schedule_run_with_overrides: an agent that allowlists only trigger_bolt_schedule_run and passes commands to it is refused. Some tools are Copilot-only (DuckDB, GitHub PR) and are not available to agents, so they do not appear here.Always-available tools
Nine core tools are available to every agent regardless of itstools block: an allowlist does not need to name them, and a denylist cannot remove them. This means an allowlist can no longer strand an agent in plan mode or silently disable Agent Skills.
Sub-agents started with
run_subagent inherit the parent agent’s tool gating, so a tightly allowlisted agent cannot reach extra tools by delegating. The explicit-allowlist-only tools (the Bolt trigger and retry tools, and the Slack thread tools) are never available to sub-agents, even when the parent allowlists them.
Filesystem & code
File System Tooledit_file comes with write_file. An agent that allowlists write_file is offered edit_file too, and denying write_file removes both, so existing agents get surgical edits without an allowlist change. An edit is refused unless the agent has already read the current version of the file in that run.
Terminal Tool
Agent-only (no dedicated tool page)
Web, search & docs
Web Search Tool
Perplexity Tool
Paradime Docs Tool
Warehouse: SQL & metadata
SQL Execution Tool
On Snowflake, an agent’s
run_sql_query waits up to 60 seconds for the result. A query that is still running after that keeps running in Snowflake, and the tool returns its query_id. The agent can do other work, then collect the rows with get_sql_query_result or stop the query with cancel_sql_query. Snowflake stops the query on its own after 15 minutes, and Paradime cancels the session’s running queries when the session stops. An agent can only collect or cancel queries that its own session started. An allowlist that names run_sql_query gets both tools without naming them. On other warehouses, a query must finish within the 5-minute tool limit.
Snowflake Tools
BigQuery Tools
Redshift Tools
Trino Tools
Databricks Tools
SQL Server Tools
ClickHouse Tools
Microsoft Fabric Tools
MongoDB Tools
dbt Discovery
dbt Discovery Tools Read-only project metadata from your Bolt runs’ dbt™ artifacts. Names and output mirror the dbt-mcp Discovery toolset.Catalog & lineage
Catalog Tool
Column Level Lineage
These read Paradime’s own catalog and lineage graph rather than the dbt™ Discovery API, so they are their own group. Scope is the production environment plus connected integrations, including dbt™ Mesh.
Bolt
Bolt ToolIntegrations
Jira Tool
HubSpot Tool
Linear Tool
Confluence Tool
Notion Tool
Google Drive Tool
Google Docs Tool
Google Sheets Tool
Slack Tools
find_slack_thread and attach_session_to_slack_thread work only in the agent’s own channels: the slack.channel in its definition, and the channel its session is bound to. An agent with neither can use them in any channel the Paradime bot is in.
Orchestration & repositories
Agent-only (no dedicated tool page)Task list
Agent-only (no dedicated tool page)
A multi-step run keeps its plan on the session rather than re-deriving it in context every turn.