Code Tools: access to internal resources

Code Tool code never connects to any other internal system directly. It is a Python handler(params, context) that runs in an isolated sandbox. The platform gives it two things at run time: getAuthHeader(alias) for auth, and context for everything else. Internal data is reached only through Leena's own HTTP APIs, the same way the code calls Workday or ServiceNow.

How a run gets its auth

The code gets a helper, never a stored credential.

1. Tool is bound to a connection. When the tool is saved, each alias (e.g. workday, leena) points to a Leena AI Integrations connection.
2. AI Colleague calls the tool. The AOP tool call sends params, bot_id and the user to the code-exec gateway.
3. Gateway resolves auth. It gets each bound connection's auth from Leena AI Integrations. This region's Leena hosts travel with the run.
4. Sandbox injects the helpers. getAuthHeader(alias) and context (bot_id, user_profile, Leena hosts) are added before the code runs.
5. Code calls the API. requests with those headers. Tokens are redacted from output and logs; the return value goes back.

Credentials stay in Leena AI Integrations until the gateway resolves them for one run; the code only ever calls the injected helper.

What getAuthHeader is

getAuthHeader(alias) is a helper function the sandbox adds to Python's built-ins, so the code calls it without importing or defining it. It returns the auth for the Integration connection bound to that alias.

def handler(params, context):
    auth = getAuthHeader("workday")
    r = requests.get(url, headers=auth)

• No stored secrets. No key or token is written in the code or stored in Leena's database.
• Hidden from output, not from the code. The token is inside the sandbox. The guarantee is that it is removed from all output, logs and error traces, so it never leaves the run.
• Second helper. context.call_connection(alias, method, path) makes the authenticated call itself.

Reaching Leena's own resources

Internal resources are reached through context and the bot's leena-x-app-secret connection. Hosts and bot IDs are never hardcoded, because they differ by region and customer.

Code Tools are not given MongoDB IDs directly. They do get the bot ID and the user's details as context, listed below.

Leena AI connector actions

Code Tools can use whatever the pre-built Leena AI connector exposes. The code calls the same Leena APIs as the connector's actions: