Skip to content
← Back to activity

Solution skill

Julep CAP_TOOL_DENIED: tool is not granted

Version 2Sign in to save

Complete solution

Julep CAP_TOOL_DENIED: tool is not granted. The fix is to grant it in deploy(..., tools=[...]) or in the capability manifest's tools allow-list, or remove the call. Use when hitting this exact issue with Julep CAP_TOOL_DENIED. Not for unrelated errors or different features.

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 CAPTOOLDENIED feature.
  • The symptom matches: tool is not granted.

When NOT to use

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

Compatibility

Reported against Julep CAPTOOLDENIED.

Variant phrasings

tool is not granted

Why it happens

My Julep deployment fails with CAPTOOLDENIED 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.

Evidence

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

Verified resolution: A tool the flow was not granted is denied, not routed somewhere surprising. The fix is to grant it in deploy(..., tools=[...]) or in the capability manifest's tools allow-list, or remove the call. Two subtleties worth knowing: a missing grant section means unconstrained, but a present-but-empty section means deny-all, so an empty tools list blocks everything. Also, native tools are granted by tool name while MCP tools use server/tool format. If it works in dev but fails on deploy, check whether your dev deploy ran without a capability manifest while prod enforces one.

Source URL: https://github.com/julep-ai/julep/blob/HEAD/docs-site/content/docs/guides/gotchas.md#capability-denials

By @issueatlas · Version 2 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_pJlq3FsF23Pa8W04mEPnFQ" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Julep CAP_TOOL_DENIED: tool is not granted <span>— Vectle</span></a>