Tool reference

Why this page matters

An agent’s capabilities are exactly the tools it can call. Instructions describe intent; tools determine what’s possible. Before writing an agent, check that the work you have in mind maps onto something here — otherwise the agent will try, fail, and narrate the failure. Use these names in an agent’s allowed-tools. Omitting allowed-tools inherits the default set rather than granting everything.

Availability differs slightly by surface. Tools that operate on a cloned target repository or on your organization’s connections are available to cloud agents; the CLI runs against your working directory instead.

Reading and searching code

Tool	What it does
`shell`	Runs a shell command in the agent’s environment. The general-purpose escape hatch — reading files, running builds, invoking any CLI. Output is truncated past a limit, and a blocked-pattern list rejects dangerous commands.
`ripgrep_search`	Fast regex or literal search across the repository, returning file, line number, and matching text. `.gitignore`-aware. The right choice for plain search, and the fallback for languages without a tree-sitter grammar.
`read_pdf`	Extracts text from a PDF — useful for threat models, policy documents, and vendor reports.

Understanding code structure

code_lineage provides three structural operations backed by tree-sitter. Coverage is limited to languages with a grammar; on anything else, use ripgrep_search.

Operation	What it does
`find_symbol`	Finds where a function, method, or class is defined and every place it’s referenced.
`call_graph`	Traces callers or callees of a symbol to a bounded depth (1–3). `direction='callers'` finds what invokes it; `callees` finds what it invokes. Computed on demand — no persistent index.
`ast_query`	Runs a tree-sitter S-expression query against one file and returns captured nodes with line ranges. For precise structural search, like every call expression in a file.

This is how an agent traces taint: find the sink, walk callers back toward a source, and confirm nothing on the path neutralizes the input.

Scanning

Tool	What it does
`opengrep_scan`	Runs OpenGrep static rules over the repository for a fast first pass, returning matches for the agent to triage. Defaults to the broad `auto` ruleset. Does not record findings — it produces candidates.
`run_opengrep_detection`	Runs one stored OpenGrep detection and emits matches as findings linked to that detection. Refuses non-OpenGrep detections.
`check_opengrep_rule`	Re-runs a stored detection’s rule against a single file, read-only. Zero matches means a fix worked. This is the verification half of patch generation.
`secrets_scan`	Runs a deterministic secrets scanner over the checkout and files one masked finding per leaked credential (API keys, tokens, private keys). In chat it scans an attached workspace; in a worker, the run’s checkout. Takes no options. Driven by the `secrets-scan` skill.
`sca_scan`	Runs a deterministic software-composition-analysis scanner over the checkout’s dependency lockfiles and files one finding per known-vulnerable package, anchored at the package’s lockfile entry, with the fixed version as the remediation. Defaults to high and critical severities; `minSeverity` and `ignoreUnfixed` narrow or widen it. The vulnerability database is fetched at scan time. Driven by the `sca-scan` skill.

Reading the outside world

Tool	What it does
`web_fetch`	Fetches a URL and extracts its text. Accepts custom headers and an extraction mode.

web_fetch performs reads only — it takes a URL, headers, and an extraction mode, with no request method or body. There is no general-purpose tool for writing to a third-party API. Agents write to other systems only through integration tools for connected apps and through workflow outputs.

Your vendors’ data

Tool	What it does
`list_leen_connections`	Lists the vendor connections configured for your organization, returning each connection’s id and vendor. The discovery step before either query below.
`get_leen_vulnerability_findings`	Queries normalized vulnerability findings from a connected vendor. Filters by severity, state, and whether a fix is available; paginates with a cursor.
`get_leen_vulnerability_finding`	Fetches one vendor finding in full.

These three are the entire vendor-data surface today, and they are scoped to vulnerability findings. See what agents can read for what that covers and what it doesn’t.

Integrations

When an organization admin connects a third-party app, its tools join this list for every agent in the organization. They’re named <App>_<Action>, and each app’s page lists them in full:

App	Tools	Examples
Slack	11	`SlackApi_SendSlackMessage`, `Slack_GetThreadMessages`
Atlassian	36	`Jira_CreateIssue`, `Jira_SearchIssuesWithoutJql`, `Confluence_CreatePage`
Linear	20	`Linear_CreateIssue`, `Linear_TransitionIssueState`
Notion	10	`Notion_SearchByTitle`, `Notion_AppendContentToEndOfPage`
Asana	8	`Asana_CreateTask`, `AsanaApi_AddTaskComment`
Google Docs	11	`GoogleDocs_GetDocumentAsDocmd`, `GoogleDocs_CommentOnDocument`

None of these delete, remove, or archive anything. If an app isn’t connected, its tools are absent rather than failing. See using integration tools in an agent for how to grant them and add a Slack or Jira step to a workflow.

Projects

Tool	What it does
`list_projects`	Lists the repositories connected to your organization, with ids, `owner/repo` names, and clone URLs.
`clone_project`	Clones a repository into the workspace so the agent can read and search it.

Recording results

Tool	What it does
`report_finding`	Records a confirmed vulnerability, with evidence. This is what makes a result durable rather than conversational.
`list_findings`	Lists findings already recorded.
`report_patch`	Attaches a verified remediation patch (a unified diff) to the finding(s) it fixes. Call it only after editing the file and confirming the fix. It stores the patch; it does not verify.
`emit_artifact`	Records a result of a kind your agent declares in `produces:` — Console’s own kinds or one you’ve defined yourself. Rejects `amplify:finding`: findings always go through `report_finding` instead.
`list_artifacts`	Lists recorded artifacts, optionally filtered by kind.
`get_artifact`	Fetches one artifact’s full content by id.

Detections

Tool	What it does
`create_detection`	Stores a new detection.
`list_detections`	Lists stored detections with id, name, description, and type.
`get_detection`	Fetches one detection, including its rule body.
`delete_detection`	Removes a detection.

Coordination

Tool	What it does
`spawn_agent`	Spawns a sub-agent on a focused task and returns its summary. How a broad job fans out without one agent losing the thread.
`spawn_multiple_agents`	Spawns several sub-agents. Used to run one child per item — a policy evaluator per detection, for instance.
`fan_out_agent`	Dispatches one agent to run against one or more of your projects, each in its own isolated cloud sandbox with a fresh checkout, and returns a summary when every run settles. How a chat reaches other projects’ code and organization skills.
`activate_skill`	Loads a skill into the agent’s context on demand.
`add_todo`, `start_todo`, `complete_todo`, `clear_todos`	Maintains the agent’s plan as a visible todo list you can watch while it works.

Managing agents

Tool	What it does
`create_agent`, `get_agent`, `list_agents`, `update_agent`, `delete_agent`	Lets an agent read and write agent definitions — so an agent can help you author another one.

Managing skills

Tool	What it does
`create_skill`	Saves a new skill to your organization from a full `SKILL.md` plus any bundled files, which the CLI reads from your machine. The frontmatter `name` must be free.
`list_skills`	Lists the skills this CLI session can activate — labelled `builtin` or `local` — beside the skills saved to your organization.

Both are CLI-only and work while signed in. They’re how the built-in skill-creator skill does its work; see organization skills.

Next steps

Write an agent

Put these names in allowed-tools.

Skills

Package a procedure an agent can load on demand.

Get Started

Agents & detections

Data & connections

Integrations

Working interactively

Workflows

Why this page matters

Reading and searching code

Understanding code structure

Scanning

Reading the outside world

Your vendors’ data

Integrations

Projects

Recording results

Detections

Coordination

Managing agents

Managing skills

Next steps

Write an agent

Skills

​Why this page matters

​Reading and searching code

​Understanding code structure

​Scanning

​Reading the outside world

​Your vendors’ data

​Integrations

​Projects

​Recording results

​Detections

​Coordination

​Managing agents

​Managing skills

​Next steps

Write an agent

Skills

Why this page matters

Reading and searching code

Understanding code structure

Scanning

Reading the outside world

Your vendors’ data

Integrations

Projects

Recording results

Detections

Coordination

Managing agents

Managing skills

Next steps