SolutionEngine LogoSolutionEngine
HomeProductUse CasesPricing

Agent Tools

Agent tools are optional capabilities you attach to an AI agent. They define what the agent can call during execution.

This page replaces the older generic “MCP Servers” explanation with the current product reality.

In the current SolutionEngine implementation, the app exposes a small built-in tool registry for agents. These tools are configured in the agent UI and then used by agent executions.

Available Built-In Tools

At the moment, the built-in registry contains these tools:

HTTP Requester

Use this when the agent needs to call external APIs or web services.

Current capabilities:

  • GET
  • POST
  • PUT
  • PATCH
  • DELETE

Current configuration fields:

  • default headers
  • request timeout

Terminal Access

Use this when the agent needs to execute shell commands.

Current configuration fields:

  • working directory
  • execution timeout

This tool is powerful and should be attached only when the workflow truly requires command execution.

Terminal access gives an agent the ability to execute shell commands. Only enable it for trusted workflows and tightly scoped operational tasks.

How Tools Are Attached

In the current app, tools are attached while creating or editing an agent.

Flow:

  1. Open the agent form.
  2. Use Add Capability.
  3. Pick a tool from the built-in list.
  4. Fill in the tool configuration fields.
  5. Save the agent.

Tools are stored with the agent definition. The workflow only references the agent, not each tool individually.

What This Means For Execution

An agent can only use the tools attached to it.

Practical implications:

  • if a tool is not attached, the agent should not rely on it
  • tool configuration is part of the agent setup, not the workflow node setup
  • changing an agent's tools changes the behavior of workflows that reference that agent

Product Terminology Note

Some internal APIs and files still use the term mcp because the capability layer was originally named around MCP.

For docs and user-facing guidance, the more accurate term for the current product is:

  • Agent Tools

That is the term users now see in the UI and the one this documentation should use.

Related Pages

PreviousEnvironment Setup and Agent Install
NextCondition Node