deco-cx / deco-cx/admin-feedback

🐛 MailMind MCP: Workflow Tools - Permission Errors

Open
#1 0 comments 0 reactions 0 assignees View on GitHub
bug mailmind permissions workflows
Dominant language
No language data
Stars
0
Forks
0
PR merge metrics
No merged PRs in 30d

Description

## 📋 Descrição

Ao testar a integração MailMind MCP no admin, identificamos **erros de permissão (403 DATABASES_RUN_SQL)** em 3 tools específicos relacionados a workflows.

## 🔴 Problema

**62.5% de falha nos testes** - 3 de 5 tools falhando com erro:
```
403 DATABASES_RUN_SQL - Falta de permissões
```

## 🛠️ Tools com Erro

- [ ] `DECO_CHAT_WORKFLOWS_START_EMAIL_SUMMARY_WORKFLOW`
- [ ] `DECO_CHAT_WORKFLOWS_CANCEL_EMAIL_SUMMARY_WORKFLOW`
- [ ] `DECO_CHAT_WORKFLOWS_RESUME_EMAIL_SUMMARY_WORKFLOW`

## ✅ Tools que Funcionam

- ✅ `GET_RECENT_EMAILS`
- ✅ `PROCESS_EMAILS`
- ✅ `SEND_EMAIL`

## 🔍 Stack Trace Completo

```
Error: 403 DATABASES_RUN_SQL
Workspace: jonasjesus-4493
Reason: Insufficient permissions to execute workflow operations
```

## 📊 Métricas de Teste

| Status | Count |
|--------|-------|
| ✅ Success | 2 |
| ❌ Failed | 3 |
| **Total** | **5** |
| **Taxa de Sucesso** | **40%** |

## 📝 Ações Requeridas

- [ ] Revisar permissões de acesso aos workflows no MCP
- [ ] Verificar configuração de DATABASES_RUN_SQL
- [ ] Testar fluxo de autorização dos 3 tools com erro
- [ ] Documentar limitações de permissão se aplicável
- [ ] Atualizar schema de acesso se necessário

## 📌 Contexto

- **Workspace**: jonasjesus-4493
- **Data do Teste**: 2025-11-07
- **Integração**: MailMind (i:b7e9fa5b-4db3-461d-9a6e-deb5cfbceffc)

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reproducing the three failing workflow tools in the MailMind MCP integration: DECO_CHAT_WORKFLOWS_START_EMAIL_SUMMARY_WORKFLOW, CANCEL_EMAIL_SUMMARY_WORKFLOW, and RESUME_EMAIL_SUMMARY_WORKFLOW. Compare their authorization requirements with the working email tools and inspect the DATABASES_RUN_SQL permission configuration. Done means the tools authorize successfully, or the applicable permission limitation is documented.

Written by the indexing model from the issue text.

Assessment

Domain
api, backend, security
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.