Where Do You Draw the Line on Agent Permissions? Devs Weigh In on MCP's All-or-Nothing Token Problem
anishtr4 · reddit · 2026-11-23
A developer wiring agents into Gmail, GitHub, Notion and Slack via MCP flags a core problem: token access is all-or-nothing — once the agent holds the token, reading a doc and emailing your entire contact list look identical to the app. His personal hard line is anything irreversible: sending email, merging to main, payments require human approval; reads, drafts and rollback-able edits are fine. The thread compares current mitigations — per-agent tokens, human-in-the-loop prompts, read-only scopes — vs. simply trusting the agent. The author is building in this space and discusses trade-offs in the comments.
More from coding & agent
- Stanford's free RAG lecture goes beyond chunking: BM25, HNSW, and agents — stanfordnlp · 2026-11-23
- Don't trust your agent's 'verified' claim: 5 practical rules for AI self-verification — dotey · 2026-11-23
- 44-Minute 3D Scene: Blender MCP + ThreeJs + Self-Built Skill Codex Workflow — OpenAIDevs · 2026-11-23
- NomosGuard: Fail-Closed Security Core Where the LLM Writes Evidence but a Rules Engine Decides — Emergency-Tutor-7 · 2026-11-23
- Wrapflow Beta: A Remote MCP Server That Gives ChatGPT and Claude a Database, Backend and Hosting — SupPandaHugger · 2026-11-23
- Inkling-2-Mini hits 10.04x on KernelBench-Mega locally, beating Grok 4.7 and GPT-6.1 — ziqiao_ma · 2026-11-23