Core Concepts

What Is Tool Use?

The ability of an AI agent to interact with external tools and APIs — reading data, calling functions, and taking actions in the real world.

In Plain English

An LLM without tools can only generate text. An LLM with tools can check your calendar, query a database, send a message, or deploy code. Tool use is what transforms a chatbot into an agent.

In OpenClaw, tool use happens through MCP (Model Context Protocol). The agent discovers available tools, decides which ones to use, and calls them with appropriate parameters. The tool returns results that the agent incorporates into its reasoning.

Every tool call is a potential security surface. An agent with database access could drop a table. An agent with email access could send to wrong recipients.

Why It Matters for OpenClaw

Tool use is the defining feature that separates agents from chatbots. It is also the biggest security risk. Every tool the agent can access is an attack surface that needs monitoring and control.

How Clawctl Helps

Clawctl provides 200+ pre-configured tool integrations via MCP. Every tool call is logged in the audit trail. Risky tool actions require human approval. Egress filtering ensures tools only reach approved external domains.

Try Clawctl — 60 Second Deploy

Common Questions

What tools can an OpenClaw agent use?

Any tool with an MCP server. Clawctl provides 200+ pre-built integrations including GitHub, Slack, Stripe, Google Workspace, and more.

Can the agent use tools I build?

Yes. Build a custom MCP server for any API or tool and connect it to your OpenClaw agent.

How do I control which tools the agent uses?

Configure allowed tools in your openclaw.json. Clawctl adds approval workflows for risky tool operations.