Tool input overrides

Tool description overrides change what the model reads. Tool input overrides change what the model can send. Where description overrides shape selection (which tool to call), input overrides pin specific arguments (what value a field carries when the call runs).

An input override hardcodes one or more fields on a tool. When an employee’s AI calls that tool, Workforce overwrites those fields with your values before the call reaches the provider. Whatever the model produced for an overridden field is replaced. This is how you guarantee every call lands on the same workspace, project, or view without trusting the model to fill the field correctly.

What an override does

For each field you configure, you give a value. At execution time that value replaces whatever the model sent for the field. What you type is coerced to the field’s type when you save, so "25" is stored as 25 when the schema expects an integer. Fields you do not configure pass through untouched.

Overrides are keyed by field path, with dot notation for nested fields. The stored shape for a tool that takes an input_data object looks like this:

{
  "input_data.view": "cases",
  "input_data.fields": ["id", "status"],
  "sort.field": "created_at"
}

A configured field is always replaced. There is no “fill only when the model omits it” behavior, so treat an override as a hard pin rather than a default.

When to use them

Pin a fixed value

Your organization has one Slack workspace, and no employee’s AI should be choosing which workspace a message goes to. Pin workspace_id on slack__post_message to your workspace ID. Every call uses that value, even when the model tries to set a different one.

Hold a field constant

If every call should write to the same project, board, or view, pin that field once on the tool instead of hoping each employee’s system prompt repeats it.

Scope

An override is set per Connector and tool, and it applies organization-wide. There is at most one override per Connector and tool combination. Overrides are not scoped per Tool Pack: an overridden tool behaves the same way in every Tool Pack in your organization.

Configure in the dashboard

Open the Connector from Connectors, stay on its Overview tab, pick the tool, and set values for the fields you want to pin.

What input overrides do not do

They do not hide the field from the model. The model still sees the field in the tool schema, and its value is replaced at execution time.
They do not narrow enums or rename fields. A configured field is replaced with one fixed value, nothing more.
They do not relax the tool’s schema. An override is validated against it when you save, so a field path the schema does not declare, or a value that cannot be coerced to the field’s type, is refused in the dialog rather than at call time.
They are not a substitute for a purpose-built tool. If you find yourself pinning many fields to reshape a tool, a Connector with a tool built for the job is the better fit.

Decide which employees reach this tool at all with Groups and access.