Why tools need approval
Most tools require approval by default. This means every time the agent would call a tool, it asks first rather than running silently. You can see the tool name and a short preview of what it is about to do before you decide. Some tools — such as the image generation widget and certain internal context tools — have approval turned off by default and run without prompting. The tools you see in a conversation depend on what the agent’s administrator has enabled.Tool parameters configured by an administrator are shown in the approval card for transparency, but you cannot edit them. Only the agent’s administrator can change those settings.
The approval card
When the agent requests to run a tool, a card appears inline in the conversation: Run{tool}?
“The agent wants to run this tool. Review the request and choose how to proceed.”
Below the description, a monospace block previews the key input the tool will use (for example, a file path, a command, a URL, or a query). Three buttons follow:
After you respond, the card collapses into a compact status line — “Approved:
{tool}” or “Denied: {tool}” — so the conversation stays readable.
Reviewing what you have already approved
Open Skills & tools from the ＋ menu in the composer. The Approved for this chat section lists every tool you have pre-approved in this conversation, with a Revoke button next to each one. Revoking a pre-approval means the agent will ask again the next time it wants to call that tool.Next steps
Skills and tools
Enable or disable individual tools and skills for a conversation.
Context compaction
Keep the conversation within the model’s context window.