ByteNex › Docs › Undeclared Tool Calls: When a Tool Is Invented
Undeclared Tool Calls: When a Tool Is Invented
An undeclared tool call is a tool that is invoked without being declared in a flow. The kernel rejects it before execution.
Undeclared Tool Calls: When a Tool Is Invented
An undeclared tool call is a tool that is invoked without being declared in a flow. The kernel rejects it before execution.
What is a declared tool?
A tool that is signed, verified, and referenced by a declarative flow. It has a defined contract and expected outcome.
What happens to an undeclared call?
It is rejected. A tool that is not declared has no expected outcome to verify against.
Does this prevent all wrong calls?
It prevents invocation of undeclared tools. Verification still applies to declared tools to confirm their outcome.
Why is this necessary?
Because an undeclared tool has no contract and no expected outcome. The kernel cannot verify its behavior or learn from the result.
Can a flow invent a tool?
No. The flow names the tools and the order. The tools must be declared. The flow itself does not execute code.