Reports what this deployment actually mounted: every subsystem the composition…
Reports what this deployment actually mounted: every subsystem the composition root declared and whether it is switched on.
GET /v1/tools/plugins
| Address | https://api.hanzo.ai/v1/tools/plugins |
| Method | GET |
| Operation | get_tools_plugins |
| Auth | Authorization: Bearer $HANZO_API_KEY |
Reports what this deployment actually mounted: every subsystem the composition root declared and whether it is switched on. A plugin here is MOUNTED CODE that extends the deployment's own surface — not a tool an agent calls — so this is an inventory and not a tool source. It is read off the same boot snapshot every traced request resolves its subsystem label against, so it cannot drift from what is serving. Enabled-only by default, because a caller asking what this deployment can do wants what is running; ?all=true adds the configured-but-off ones.
Request
1 field.
| Field | In | Type | Required | Description |
|---|---|---|---|---|
all | query | string | — | All includes the configured-but-disabled subsystems too, but only when it is exactly the string "true". |
Response
| Status | Body | Meaning |
|---|---|---|
200 | pluginMountList | ok |
200 body — 4 fields.
| Field | In | Type | Always | Description |
|---|---|---|---|---|
plugins | body | pluginMount[] | — | Plugins is every subsystem the composition root declared, filtered to the enabled ones unless all=true. |
plugins[].enabled | body | boolean | — | Enabled is whether this subsystem is switched on in this deployment. |
plugins[].name | body | string | — | Name is the subsystem's name, the same label a traced request resolves to. |
plugins[].prefixes | body | string[] | — | Prefixes are the URL prefixes this subsystem serves. |
Failure carries the platform error shape — see Errors.
Examples
hanzo has no subcommand for this operation — the CLI serves only what cloud's live route table confirms. Use HTTP or an SDK.
import { Configuration, ToolsApi } from 'hanzoai';
const api = new ToolsApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.getToolsPlugins();from hanzoai.cloud import ApiClient, Configuration
from hanzoai.cloud.api import ToolsApi
client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = ToolsApi(client).get_tools_plugins()cfg := cloud.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := cloud.NewAPIClient(cfg)
resp, _, err := client.ToolsAPI.GetToolsPlugins(context.Background()).Execute()
if err != nil {
return err
}use hanzo_cloud::apis::{configuration::Configuration, tools_api};
let mut cfg = Configuration::new();
cfg.bearer_access_token = std::env::var("HANZO_API_KEY").ok();
let result = tools_api::get_tools_plugins(&cfg, Default::default()).await?;import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.ToolsApi;
ApiClient client = new ApiClient();
client.setRequestInterceptor(b -> b.header("Authorization", "Bearer " + System.getenv("HANZO_API_KEY")));
var result = new ToolsApi(client).getToolsPlugins();The method above is the one at the current release of the document. [email protected] (npm) and [email protected] (PyPI) were generated from an earlier release, where this operation carried a different id, so it spells the method differently — regenerating the clients is what makes the two agree. SDKs →
curl https://api.hanzo.ai/v1/tools/plugins \
-H "Authorization: Bearer $HANZO_API_KEY"The door reaches tools through the tools tool, which names its 19 operations with its own verbs — this one among them, under a name only the door declares. describe explains any of them:
curl -X POST https://api.hanzo.ai/v1/mcp \
-H "Content-Type: application/json" \
-d '{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "describe",
"arguments": {
"op": "list_mcp_servers"
}
}
}'How is this guide?