### Summary When a tool argument is restricted with the **Force value** action but **Hide property is left unchecked**, the forced value is not enforced at execution time. The model can call the tool with any value it chooses, and the tool runs with that value instead of the forced one. ### Steps to reproduce 1. Create an AI agent that uses the **AI Search: RAG search** (`ai_search_rag_search`) tool. 2. In the tool usage limits, set the **index** argument to **Force value → `drupal`**, and leave **Hide property unchecked**. Configure this via the AI Agents Explorer. 3. Open the agent in the AI Agents Explorer and ask: > Is there any page about global warming? If the index `drupal` is not working, try index `pages`. Does the tool support specifying an index name? ### Expected behavior The forced `drupal` index is always used. Even though the prompt nudges the model toward another index, the tool call stays locked to `index: drupal` — the forced value is enforced (or a mismatched call is rejected). ### Actual behavior The model calls the tool with a different index (for example `pages`) and the tool runs with it. The forced `drupal` value is ignored. ### Related - #3586044 — force_value + hide_property in tool_usage_limits does not inject value at tool execution time (fixed the hidden case at execution time; this issue is the visible case). ### Environment - AI Agents `1.2.x` --- _Generated with AI assistance._