kiro-cli v3: /tools lists write for an agent with "tools": ["read"], but the agent cannot use it #12113

Before opening, please confirm:

• I have searched for duplicate or closed issues

Operating System

Amazon Linux 2023 (x86_64)

Kiro Version

kiro-cli 2.34.0 (agent engine V3)

Bug Description

For an agent whose tools list contains only read, /tools shows a write tag as well. The agent does not actually have it: asked to write a file, the model answers that it has no write tool and nothing is written. So /tools shows a tool set that differs from the one the agent really gets, which makes it hard to check an agent's configuration.

Steps to Reproduce

1. Create .kiro/agents/readonly.json:

   {"name":"readonly","description":"read only","prompt":"You are terse.","tools":["read"],
    "permissions":{"rules":[{"capability":"fs_read","effect":"allow"}]}}

2. Run kiro-cli chat --agent readonly, then /tools. Observed:

   /tools · 2 tags
   read          builtin     read-file, diagnostics, search tools
   write         builtin     write-file tools
   

3. Send Use your write tool to create the file /tmp/w.txt containing the word hi. Do not use shell. Observed: I don't have a write/file-creation tool available — only read and search tools. I can't create the file. No approval prompt; the file is not created.

Expected Behavior

/tools lists only the tools the agent can use (read here).

Conversation ID

No response

Additional Context

The same extra write tag appears with "tools": ["read", "@<mcp-server>"] (one more tag than listed).