Where tools run
Tools are available across Erstan, but the control surface changes by context.Tool sources
Erstan groups tools by source so builders can tell what owns the operation and which authorization model applies.By Erstan
First-party tools built into Erstan for tasks, projects, documents, files, workbooks, teams, skills, agent runs, Agent Builder, and SuiteQL helpers.
By connector
Tools exposed by connected systems or providers, including NetSuite MCP, Slack, OpenAI, Anthropic, business apps, and custom MCP servers.
Read, write, notify, and attach behavior
Every tool has an operational shape. The shape is not only documentation: it informs approvals, connector policy, and how you design an agent flow.Tool access in Agent Builder
AI steps can be configured with different levels of tool access:
For production agents, pin the exact tools a step needs and describe when to use them in the step instructions.
Managing access
Owners and admins control connector availability and per-tool write policy from Connectors. Builders control which tools a specific agent step can use. End users approve write actions when a policy or agent step requires a human checkpoint. For Agent Builder guidance, see Choosing AI steps and Giving agents tools, skills & connections.Next steps
Tools by Erstan
Review the first-party Erstan tool catalog.
Tools by connector
Review connector-backed and provider-backed tools.
Choosing AI steps
Decide when an agent should think, respond, call tools, branch, loop, or pause.
Connectors overview
Connect systems and manage tool write policy.