[bug] Auto-approval is failing for access_mcp_resource

[s97712]

App Version

v3.3.1

API Provider

Anthropic

Model Used

Claude 3.7 Sonnet

🔁 Steps to Reproduce

The access_mcp_resource is not being automatically approved, despite all auto-approval groups being enabled.

💥 Outcome Summary

Auto-approval

📄 Relevant Logs or Errors (Optional)

[dosubot]

Based on the docs, MCP tool auto-approval is controlled by both a global toggle and a per-tool "Always allow" setting. Even if all auto-approval groups are enabled, auto-approval for access_mcp_resource will only work if the global "Use MCP servers" auto-approval option is on and the "Always allow" checkbox is checked for that specific tool in the MCP server settings. The master toggle in the Auto-Approve Toolbar must also be enabled for permissions to take effect. If any of these are off, auto-approval won't trigger as expected. See the relevant setup steps and screenshots in the docs for more detail: auto-approving actions, using MCP in Roo.

There are no documented bugs or known issues with auto-approval or group-based permissions in v3.3.1 or with Claude 3.7 Sonnet. If all settings look correct, try toggling them off and back on to rule out UI sync issues. If the problem persists, enabling debug or verbose logging (if available) may help surface silent failures. If you can share any logs or error output, that could help narrow things down.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}   

[daniel-lxs]

The auto-approval mechanism for access_mcp_resource is failing because MCP resources currently lack the UI controls and backend support for individual "Always Allow" settings that MCP tools have.

When the frontend checks if an MCP request should be auto-approved at https://github.com/RooCodeInc/Roo-Code/blob/main/webview-ui/src/components/chat/ChatView.tsx#L846-L865, it only handles use_mcp_tool requests by checking the tool's alwaysAllow property. For access_mcp_resource requests, there's no equivalent check because resources don't have this property or UI control.

To fix this issue, the following changes are needed:

1. Update the MCP resource types to include an alwaysAllow?: boolean field in McpResource and McpResourceTemplate types.

2. Enhance the UI component McpResourceRow.tsx to display an "Always Allow" checkbox when the global MCP auto-approval is enabled, similar to how McpToolRow.tsx works.

3. Add backend message handling for a new toggleResourceAlwaysAllow message type to persist the user's preference in the MCP settings file.

4. Update the auto-approval logic in ChatView.tsx to handle access_mcp_resource requests by checking the resource's alwaysAllow property.

This will provide users with granular control over which MCP resources can be auto-approved, matching the functionality already available for MCP tools.