# Why MCP security is about permissions overhaul

DevFeed: [Why MCP security is about permissions overhaul](<https://devfeed.tech/articles/why-mcp-security-is-about-permissions-overhaul-109604.md>)

Original publisher: [Read original article](<https://www.webflow.com/blog/mcp-security>)

Author: Mohit Bansal

Published: 2026-09-09T00:00:00Z

Content type: article

Language: en

Sources: [Webflow Blog](<https://devfeed.tech/sources/webflow-blog.md>)

Topics: [Security](<https://devfeed.tech/topics/security.md>), [Access Control](<https://devfeed.tech/topics/access-control.md>), [MSP MCP](<https://devfeed.tech/topics/msp-mcp.md>), [credential-based attacks](<https://devfeed.tech/topics/credential-based-attacks.md>), [principle of ephemerality](<https://devfeed.tech/topics/principle-of-ephemerality.md>), [tenant data protection](<https://devfeed.tech/topics/tenant-data-protection.md>), [trust](<https://devfeed.tech/topics/trust.md>)

Tags: [access-controls](<https://devfeed.tech/tags/access-controls.md>), [accountability](<https://devfeed.tech/tags/accountability.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agent-identity](<https://devfeed.tech/tags/agent-identity.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [authorization](<https://devfeed.tech/tags/authorization.md>), [confused-deputy-problem](<https://devfeed.tech/tags/confused-deputy-problem.md>), [credentials](<https://devfeed.tech/tags/credentials.md>), [mcp](<https://devfeed.tech/tags/mcp.md>), [mcp-security](<https://devfeed.tech/tags/mcp-security.md>), [permissions](<https://devfeed.tech/tags/permissions.md>), [redesign](<https://devfeed.tech/tags/redesign.md>), [security](<https://devfeed.tech/tags/security.md>)

## AI overview

The article argues that MCP security failures often stem from credentials with excessive or stale permissions, rather than protocol defects. It cites incidents involving GitHub repository access and Asana cross-tenant access, then recommends task-specific secrets, authorization for each action and user, and temporary credentials. Its review questions cover current credential scope, per-site or per-repository controls, whether agents inherit or bypass a person's permissions, attributable activity logs, and review steps before production changes. It also identifies an unresolved identity problem: agents often borrow human OAuth credentials, while standards for agent identity and task-linked token lifetimes remain early proposals. The article recommends treating agent lifespan as an input to access decisions, while noting that no clean model for balancing lifespan and access is established.

## Source excerpt

Most MCP breaches trace back to over-scoped credentials, not broken code. Here's what a real permissions redesign checks for.