andibase

Agent Tools

Current runtime tools exposed to workspace agents

Open Markdown

This page describes the current tool surface exposed to agents at runtime.

Tool availability depends on two things:

  • the authenticated caller for the chat
  • whether the chat has a resolved workspace context

Current runtime tools

ToolRequiresWhat it does
bashbuilt-in builder agentExecutes shell commands inside an in-memory sandbox. When AI Gateway auth is configured, curl can call the configured allow-list with server-side header transforms.
readFilebuilt-in builder agentReads files from the bash sandbox, including /workspace/SKILL.md.
writeFilebuilt-in builder agentWrites files inside the bash sandbox, including edits to /workspace/SKILL.md during the current agent run.
get_data_definitionsdata.readLists data definitions in the current workspace. By default it returns compact summaries (handle, name, url, description); pass includeFields: true to get full definitions with fields and metadata.
list_data_recordsdata.readLists records for one data definition with pagination, filtering, and sorting.
query_data_recordsdata.readSame record-query surface as list_data_records, exposed under an explicit query-oriented name.
create_data_recordsdata.writeCreates one or more records in a data definition.
update_data_recordsdata.writeUpdates one or more existing records by id.
delete_data_recordsdata.writeSoft-deletes one or more existing records by id.
workspace_access_unavailableno workspace contextReturns a structured error when the chat does not have a resolved workspace context.

Capability flags on agents

Agent definitions also store capability flags.

Capability flagMeaning today
objectsAccessRepresents structured workspace-object access. The current runtime tools on this page are the active object/data tools.
webAccessStored on the agent definition, but the bash sandbox tools are currently reserved for the built-in builder agent.
browserAccessStored on the agent definition, but not currently exposed as a runtime tool in this tool set.

Permission model

  • Session users get the same data read/write access they already have in the workspace.
  • API-key-backed callers get tools only for the permissions granted to that key.
  • Agents do not get broader access than the authenticated caller for the chat.

See also:

On this page