Tools, knowledge, and skills
Give an agent controlled access to actions, documents, MCP integrations, and workspace skills.
Agents become useful when they can do more than answer from memory. In Automate, you extend an agent with Tools, Knowledge, and Skills from the Configure page.
Use the least access that solves the job. A focused agent is easier to test, easier to explain, and safer for teammates to use.
What each area is for
| Area | Use it when |
|---|---|
| Tools | The agent should take an action, call an app, run a workflow, or use an MCP integration |
| Knowledge | The agent should answer from uploaded documents or saved text |
| Skills | Your workspace has reusable capability packs enabled |
| Objects | The agent should read or update structured business records |
This guide focuses on the high-priority setup for tools, knowledge, MCP, and skills.
Open the configuration areas
Open the agent
Go to Agents, then open the agent you want to configure.
Open Configure
Click Configure.
Choose an area
Use the side areas on the configuration map: Tools, Knowledge, or Skills.
Use Tools for actions and MCP, Knowledge for notebooks, and Skills when the workspace enables them.
Tools
Tools are actions the agent can call. Some tools are built into Automate. Others come from apps, workflows, or MCP servers.
Before you enable a tool, ask:
- What exact job should the agent use this tool for?
- Should the agent ask the user before taking the action?
- Does the tool need a connection owned by the user or workspace?
- What would a safe failure look like?
Add tools gradually. Test each one with a prompt that should use it and a prompt that should not use it.
MCP integrations
MCP integrations appear under Tools as MCP Integrations. They let an agent use tools from an external MCP server.
There are two layers:
| Layer | Where it happens |
|---|---|
| Connect your account to an MCP server | MCP under Connect |
| Enable that MCP server on an agent | Agent Configure → Tools → MCP Integrations |
When you enable an MCP integration, choose the connection if Automate asks. Use Default only when your team has agreed which connection should be used.
Knowledge
Knowledge gives the agent documents or saved text to search. Uploading files to a notebook is not enough by itself; the notebook must also be enabled on the agent.
Create or prepare a notebook
Create the notebook under Knowledge, then add text or files.
Open Knowledge on the agent
In the agent, go to Configure → Knowledge.
Find the notebook
Use Search notebooks... when there are many notebooks.
Enable it
Turn on the switch for the notebook. The footer shows how many notebooks are enabled.
Test retrieval
Return to Build and ask a question that should be answered from the notebook. If the answer is vague, improve the document or add clearer instructions.
Skills
Skills are reusable capability packs. If your workspace does not have Skills enabled, the Skills area may show that they are unavailable.
When Skills are available:
- Add only skills that match the agent's purpose.
- Keep instructions clear about when the skill should be used.
- Test a prompt that should trigger the skill and one that should not.
If you are unsure whether a skill is safe for a shared agent, ask an administrator before enabling it.
A safe access checklist
Before you share an agent, check:
| Question | Why it matters |
|---|---|
| Does the agent have only the tools it needs? | Reduces accidental actions |
| Are knowledge notebooks narrow and current? | Improves answer quality |
| Are app and MCP accounts connected? | Prevents tool failures during chat |
| Do instructions say when to ask a human? | Keeps business decisions controlled |
| Have you tested success and refusal examples? | Confirms the agent's boundaries |