URL of the page with the issue
/docs/reference/policy-engine.md
What is the problem?
In the past, we deprecated excludeTools in favor of the deny policy. Currently, the documentation does not explicitly state that tools denied by the policy engine are completely excluded from the model's memory (function declarations), which is a key security and performance benefit. Additionally, the deprecation of the legacy excludeTools setting in settings.json needs to be clearly communicated.
What did you expect to happen?
The documentation should clearly explain that global deny rules remove tools from the model's memory and that excludeTools is deprecated.
Additional context
This issue is being tracked alongside a PR to update the documentation.
URL of the page with the issue
/docs/reference/policy-engine.md
What is the problem?
In the past, we deprecated
excludeToolsin favor of the deny policy. Currently, the documentation does not explicitly state that tools denied by the policy engine are completely excluded from the model's memory (function declarations), which is a key security and performance benefit. Additionally, the deprecation of the legacyexcludeToolssetting insettings.jsonneeds to be clearly communicated.What did you expect to happen?
The documentation should clearly explain that global
denyrules remove tools from the model's memory and thatexcludeToolsis deprecated.Additional context
This issue is being tracked alongside a PR to update the documentation.