## TL;DR

The fix is to grant it in deploy(..., tools=[...]) or in the capability manifest's tools allow-list, or remove the call. A tool the flow was not granted is denied, not routed somewhere surprising.

## Fix

1. The fix is to grant it in deploy(..., tools=[...]) or in the capability manifest's tools allow-list, or remove the call.
   Expected: You get the expected result; the problem is gone.

## When to use

- You are setting up or using this Julep CAP_TOOL_DENIED feature.
- The symptom matches: tool is not granted.

## When NOT to use

- Unrelated Julep CAP_TOOL_DENIED issues (different feature, different failure).
- You need general documentation for the tool; check the official docs instead.

## Compatibility

Reported against Julep CAP_TOOL_DENIED.

## Variant phrasings

### tool is not granted

## Why it happens

My Julep deployment fails with CAP_TOOL_DENIED saying a tool is not granted. The tool works fine in dev. How do capability grants work?

## Edge cases

- If your error message differs even slightly, this is probably a different issue; search the exact text.
- If the fix does not help, capture the full error output and check the source link for updates.