permissions.allow entry not honored for MCP write tool — re-prompts every call (find_and_replace_in_doc)

Bug: permissions.allow entry not honored for MCP write tools — re-prompts every call

Summary

Selecting "Yes, and don't ask again" for an MCP tool correctly writes the tool name to permissions.allow in settings.local.json, but Claude Code continues prompting on every subsequent call for that tool.

Environment

• Claude Code CLI
• Permission mode: auto ("defaultMode": "auto" in ~/.claude/settings.json)
• skipAutoPermissionPrompt: true (confirmed this only controls the auto-mode entry dialog, unrelated)

Affected tool

mcp__google-drive__find_and_replace_in_doc

Steps to reproduce

1. Run a tool call that triggers mcp__google-drive__find_and_replace_in_doc
2. Select "Yes, and don't ask again for google-drive - find_and_replace_in_doc commands"
3. Verify entry appears in settings.local.json under permissions.allow:

``json
"mcp__google-drive__find_and_replace_in_doc"
``

1. Trigger the same tool call again in the same or a new session
2. Claude prompts for permission again despite the allow entry

Expected behavior

Tool call proceeds without a permission prompt once the entry is in permissions.allow.

Actual behavior

Prompted every call. The allow list entry is present but not respected.

Notes

• Other MCP tools in the same allow list (e.g. mcp__jira__transition_jira_issue, mcp__google-drive__get_file_comments) do NOT re-prompt — the issue appears specific to find_and_replace_in_doc or possibly mutation/write-type MCP tools.
• The sandbox write-deny list for settings.local.json was ruled out — the entry IS being saved successfully.