List a connector’s tools for writing a restriction
/restriction/connector/{slug}/tools
Every tool the connector defines — name, person-readable label, description, resource and method — for picking `tools[].tool_name` values in a restriction. Unlike `GET /connector/{slug}/tools`, this answers regardless of the CALLER’S own restrictions: that route asks “which of these may I call” and `403`s a connector the caller is blocked from, which left a member unable to narrow a rule that blocks them to specific tools. Reading the catalog grants nothing: execution, connection and toolbox pinning each still apply the caller’s restrictions, and the write routes still decide whether the caller may write the rule. Requires `restriction:manage` and `connector:view` — the second is what browsing the catalog costs everywhere else; this route drops only the caller’s use-side restriction. Cursor-paged by `name`.
Path Parameters
Connector slug.
Query Parameters
Case-insensitive substring match on tool_label, name, description and resource. LIKE wildcards are matched literally. Max 200 characters.
Response Body
Exact tool name — what tools[].tool_name must contain.
The same server-computed phrase a saved rule’s tools[].tool_label carries for this tool, so a tool reads the same in the picker as on the saved rule.
curl -X GET 'https://api.elaichi.ai/restriction/connector/<slug>/tools' \
-H 'Authorization: Bearer $ELAICHI_API_TOKEN' \
-H 'Content-Type: application/json'const response = await fetch('https://api.elaichi.ai/restriction/connector/<slug>/tools', {
method: 'GET',
headers: {
'Authorization': 'Bearer ' + process.env.ELAICHI_API_TOKEN,
'Content-Type': 'application/json',
},
});
const data = await response.json();
console.log(data);import os
import requests
url = "https://api.elaichi.ai/restriction/connector/<slug>/tools"
headers = {
"Authorization": f"Bearer {os.environ['ELAICHI_API_TOKEN']}",
"Content-Type": "application/json",
}
response = requests.get(url, headers=headers)
print(response.json())