[TEST] Elicitation Feature Request Template for Roo Code

[dipseth]

Test Issue: Elicitation Support Feature Request Template

This is a test issue to validate the GitHub token and prepare the feature request for RooCodeInc/Roo-Code

What specific problem does this solve?

Roo Code currently lacks elicitation support - a critical MCP protocol feature that enables secure user confirmation dialogs for sensitive operations like sending emails to untrusted recipients. This forces users to rely on less sophisticated fallback mechanisms and reduces security control.

Who is affected: All Roo Code users who work with email-sending MCP servers, particularly those using FastMCP2 and similar platforms with built-in security features.

When this happens:

• When users attempt to send emails via MCP tools to recipients not on their allow list
• When MCP servers try to present security confirmation dialogs
• When sophisticated email security workflows are needed

Current behavior vs Expected:

• Current: MCP servers fall back to saving drafts or blocking emails entirely
• Expected: Interactive confirmation dialog allowing users to choose: send immediately, save as draft, or cancel

Impact:

• Reduced Security Control: Users lose granular control over email sending decisions
• Poor User Experience: No interactive confirmation for sensitive operations
• Limited MCP Integration: Cannot fully utilize advanced MCP server security features
• Workflow Disruption: Manual draft review required instead of streamlined confirmation

Additional context

Real-World Evidence from FastMCP2 Implementation

Our FastMCP2 platform has implemented a comprehensive elicitation-based email security system documented in documentation/api-reference/gmail/README.md:

Security Benefits Achieved:

• ✅ Prevents Accidental Emails: No more sending to wrong recipients
• ✅ User Control: Always get confirmation for untrusted contacts
• ✅ Audit Trail: Structured responses log all security decisions
• ✅ Flexible Actions: Save drafts for manual review or send immediately
• ✅ No False Blocks: Trusted contacts always work seamlessly

Current Elicitation Response Example:

{
  "success": true,
  "message": "📝 **EMAIL SAVED AS DRAFT** (not sent)",
  "draftId": "r-5949208333949694620", 
  "recipientCount": 1,
  "elicitationRequired": true,
  "recipientsNotAllowed": ["test@example.com"],
  "action": "saved_draft"
}

Reference Implementation: See lines 367-440 in our Gmail API documentation showing complete elicitation workflow implementation.

Next Steps

1. ✅ Test GitHub token access (this issue)
2. 📝 Submit actual feature request to RooCodeInc/Roo-Code
3. 🤝 Engage with maintainers on Discord
4. 🔨 Begin implementation after approval