kortecxdocs
Beta tasks

See the tools a run can use

For a beta user: see the tools your runtime has registered, read which can fire, and know why a listed tool is not a granted one.

For a beta user who wants to know what an agent can actually call. After this page you can read the tool list and tell whether each tool can fire here. Not here: bringing a service's tools in (Connect an outside service).

Tools is family 09, which reads four bars evidenced in the census at revision 3ec0e4f4, 2026-10-20. Three of those bars read under the older census rule, not the newer one: reachable, measured and natural-language. The census console bar has no reading key.

As of 2026-10-21, this page gives the console path only. The cloud SDK and command line name no method for this family's tools. The cloud SDK is also built from source until its first publish.

List the tools

MCP in the left rail opens a page titled "Tools a run can be granted." with a Tools tab. Each tool shows where it came from: Built in, From followed by a connector's name, or Registered. An In a run column shows the word the runtime serves for whether the tool can fire in a run on this deployment.

Choose Details on a tool to see that fact in words, "Fires in a run it is granted to" or "Can't fire here", and which of the skills the page has loaded wish for it, which of the Apps it has loaded grant it, and, where one is served, the network scope of the tool. A tool's Details drawer can also offer Test: a real model run that may call the tool once, billed by your model provider (see Connect an outside service).

With no tool registered the console says "No tools are registered here yet" and "Connecting a server adds its tools here."

Presence is not permission

A tool in the list is not a tool a run holds. Tools run inside a run, as a grant.

Recording and removing

The Tools tab has no control for recording a tool.

A tool's Details can offer Remove…, which asks you to type the tool's name back. A built-in tool, and one that a connected server manages, cannot be removed there. Removing a tool is for an owner or an admin where your org has them.

What it does not do yet

Dated gaps, as of 2026-10-21. None is a step on this page.

  • Tool manifests. Reading tool manifests is not served on this deployment.
  • Driven live. Everything on this page is read from the console source and the cloud code at the cited revisions. None of it was driven against a deployed console for this page.

What it refuses

You see your own workspace's tools and the platform's built-in tools. The census tenancy check for this family reads PARTIAL: a static scope audit, with no cross-tenant probe receipt. A deployment without the tool registry says "Tools aren't set up on this deployment", or "Tools aren't on this deployment" where the route is not mounted, rather than showing an empty list.