Function tools & approvals
Client functions and first-party approved actions are different permission boundaries.
External client functions
Declare a function schema in your native request. The model may return a function call; your application validates the arguments and controls execution. Return the result with the exact call ID. NotHoly does not execute an arbitrary external function.
First-party actions
A web or companion action is governed by its mode, context and server policy. Sensitive work requires approval bound to exact inputs, policy and expiry. Source text and model output never grant permission.
Untrusted source material
Files, retrieved snippets and tool output remain untrusted context. Approved excerpts may be sent to the selected model for synthesis. Review the scope and processing disclosure before including private material.
Structured output
Guaranteed JSON schema output is not currently offered by these native contracts. Validate model output in your application and do not use a generated JSON claim as an authorization decision.