Skip to main content

Tools Reference

This page lists the model-visible tools Anyy can expose through the resident runtime. Toolsets decide visibility; risk, approval, ChangePlan, and audit policy still apply after a tool is visible.

For selection rules, see Toolsets Reference. For the current runtime catalog, use /tools, /toolsets, or the dashboard /dashboard/tools page.

Default Runtime Tools

These tools are available in the built-in runtime when their toolset is selected.

ToolsetToolsNotes
webweb_search, web_fetch, web_extractPublic web search and HTTP(S) retrieval. Private/internal network URLs are blocked by extraction.
sessionssession_searchSearches recent sessions and prior conversation messages in the current session scope.
memorymemoryStructured long-term memory edit tool with add, replace, and remove.
taskstask_create, task_list, task_update, task_completeDurable personal tasks. Writes are audited.
automationautomation_list, automation_create, automation_update, automation_delete, automation_run, automation_historyScheduled automations and reminders. Script cron jobs are not exposed to model automation tools.
messagingmessaging_status, message_receipt, notify_user, send_messageUser-visible notification and current-user/current-origin messaging. No arbitrary external contact send.
skillsskills_list, skill_view, skill_manageSkill discovery, viewing, reload, and managed-skill operations. skill_manage appears when the gateway skill resolver/manager is available; lower-level registry-only builds may expose only list/view. Exact actions depend on skill root policy.
fileread_file, write_file, search_files, patchWorkspace/local file operations. Writes and patches are high-impact and policy gated.
terminalbash, processShell execution and managed background process control. High-impact operations use ChangePlan gates.
ttstext_to_speechGenerates audio artifacts when a TTS provider is configured.
clarifyclarifyAsks the user for missing information through the active surface.
subagentsdelegate_task, background_job, subagent_list, subagent_history, subagent_cancelDelegation, async child-agent work, and child-run control.

clarify and subagents tools are appended by the gateway service, so they may not appear in lower-level registry-only tests.

Optional Connector Tools

These tools appear only when the corresponding connector or service is wired into the runtime:

ToolsetToolsWhen visible
emailemail_status, email_search, email_get, email_draft, email_sendAn email connector is wired into the runtime. email_send requires approval.
calendarcalendar_status, calendar_list, calendar_get, calendar_draft, calendar_create, calendar_update, calendar_cancelA calendar connector is wired into the runtime. Create, update, and cancel require approval.
artifactartifact_list, artifact_inspect, artifact_pinRuntime artifact service is available and the turn selects or receives the artifact toolset. Attachment turns can receive it automatically unless explicit turn toolsets were supplied.
media_generationimage_generateImage generation provider/service is configured.
computer_usecomputer_useEnabled through the computer-use setup path.
mcp-<server>mcp_<server>_<tool>MCP server is enabled and its toolset is selected.
browserAnyy browser toolsBrowser integration is enabled and activated.
mcp-browserRaw MCP browser toolsExplicit MCP diagnostics only; browser setup does not activate it by default.

Optional tools should not be documented as always available. If a connector is not configured, the runtime does not expose its toolset.

Risk And Approval Summary

Descriptor risk values are read, runtime-low, runtime-high, config-low, config-high, credential-high, dangerous, and force-required. Approval policy values are none, hook, and always. Execution policy values are direct, audit, confirm, change_plan, and force_change_plan.

ClassExamplesBehavior
Direct readweb_search, session_search, task_list, email_search, calendar_listRuns without approval; audited as runtime read when applicable.
Audited low-risk changetask_create, automation_create, memory, notify_userRuns without user approval by default but records audit events.
Confirmed connector mutationemail_send, calendar_create, calendar_update, calendar_cancelRequires approval before the connector mutation is replayed.
ChangePlan-gated host operationbash, process kill, write_file, patchRequires a ChangePlan or policy hook approval before state-changing execution.

The exact policy can also be affected by MCP server policy and tool_governance.overrides.

Output Budgets

Every descriptor can set output_budget.visible_chars and output_budget.stored_chars. Visible output is capped before it is sent back into the turn. Stored output can keep more detail for history, audit, or later reads.

If a successful visible result is larger than its visible budget, Anyy can persist the full output under ANYY_TOOL_RESULTS_DIR, or /tmp/anyy-results when that environment variable is unset. The visible result becomes a short <persisted-output> preview and metadata records persisted_output_path and persisted_output_bytes.

Tool Details

Web

web_search returns public search results. web_fetch fetches one public HTTP(S) URL. web_extract extracts readable content from up to five public HTTP(S) URLs and blocks private/internal network URLs.

Memory

The ordinary memory surface is one tool named memory. It accepts action, target, content, and old_text. Lower-level memory maintenance tools are not part of the default model-visible runtime.

See Persistent Memory.

Automation

Automation tools use the canonical schedule object:

{"type": "every", "mode": "interval", "interval": "30m"}

They reject legacy top-level schedule fields such as when, every, cron, and recurring.

See Cron.

Subagents

delegate_task is synchronous and returns child summaries to the parent turn. background_job is async and returns a background_job_id. Control tools list, inspect, and cancel child runs owned by the current session.

See Delegation and Background Jobs.

Terminal And Process

bash runs shell commands. With background=true, it creates a managed background process. process can list, poll, log, wait, kill, write to, submit to, or close managed process jobs created by Anyy.

process is not a general host process inspector.

Email And Calendar

Email and calendar tools are connector-backed. Read/status tools are direct reads. Draft tools create local connector drafts without sending. Sending email and mutating calendar events require approval.

This reference describes the model-visible tool contracts only. If a build does not supply an email or calendar connector, these toolsets are absent at runtime.