Explyt tool catalog

Tools give the agent access to the project, the JetBrains IDE, the terminal and external services. The exact set depends on the selected agent mode, the IDE, the language and the connected MCP servers.

This page helps you understand what the tools are for. Configuring access and confirmations is described separately, in the Tools menu.

Exploring the project

Tool or group	What it does	Changes state
File reading	Opens the contents of a file or a selected range of lines	No
Directory browsing	Shows the structure of files and folders	No
File structure	Shows classes, methods and other elements without reading the whole file	No
Text and file search	Searches file names and text matches	No
Declaration and usage search	Uses the IDE indexes to find symbols, implementations and references to them	No
Dependency reading	Opens the source or decompiled code of the connected version of a library	No

For details, see search with IDE indexes and reading dependency code.

Changing the project

Tool or group	What it does	What to watch out for
File creation and editing	Adds or replaces file contents	Limit the area with Edit Scope
Symbol rename	Runs the IDE refactoring and updates the related usages	Check the public API and external code

For structural changes, IDE refactorings are preferable to text replacement. When the work is done, review the result in Agent Changes.

Runs and analysis in the IDE

Tool or group	What it does	Availability
Run configurations	Gets the list of configured runs, starts an application, tests or a build	Depends on the IDE and the language
Test results	Returns a structured test result and errors	For supported configurations
Coverage	Measures coverage of the selected files and branches	Support varies by IDE
IDE inspections	Looks for errors, warnings and antipatterns	Used by the Review mode
Debugger	Sets breakpoints, starts debugging, reads values and the call stack	Used by the Debug mode
File errors	Gets the errors the IDE knows about in a source file	Depends on language support

For details, see run configurations, agent modes and the feature matrix.

Terminal

The terminal tools run commands and manage processes. You need them when there is no suitable IDE configuration or when the task involves an external utility.

A command can change files, a database, the environment or a remote system. Before running one, check:

• the command itself and the working directory;
• the environment used;
• whether it can write or delete data;
• whether it connects to external systems;
• how to stop a background process.

The exact rules for automatically allowing terminal commands depend on the tool's settings. Check the actual state in the Tools menu.

Internet and browser

Tool or group	What it does	Notes
Web Search	Searches for sources on the internet	Search results need to be verified against the primary source
Web Fetch	Reads an accessible page	Not a replacement for an interactive browser
Browser MCP tools	Open pages, fill in forms, click elements, read the network and the console	Can change data in an external service

For details, see Web Search and MCP.

MCP tools

Once an MCP server is connected, its tools appear in the Tools menu as a separate group. The names, parameters and consequences of a call are defined by the server itself, so there is no single complete catalog for them.

Before using MCP:

1. check the source of the server;
2. grant minimal rights;
3. look at the list of tools;
4. keep confirmation on for actions that change external data;
5. run the first request in a safe test environment.

Which tools are available to which modes

In short:

• Ask and Review do not edit files;
• Debug controls the debugger;
• Review can run IDE inspections;
• General can pass subtasks to subagents;
• Orchestrator coordinates subagents but does not run ordinary tools directly.

The exact availability table is in the Agent Modes section. To check whether a feature is available in a specific IDE, see the other tables in the matrix.

Access and confirmations

The fact that a mode has a tool does not mean every call runs automatically. An individual tool can be set to allowed without confirmation, to ask for confirmation, or to forbidden.

The documentation does not fix a single set of defaults across all Explyt versions and configurations. Before a sensitive task, open the Tools menu and check the actual settings.

Additional restrictions:

• Edit Scope — the file editing area in the current task;
• .readignore and .writeignore — a permanent ban on reading or writing paths;
• permissions and safety — the general action control model.