TL;DR: Poisoned tool content, malicious servers, and exposed secrets all steer agent behaviour in PipeLab's 2026 MCP snapshot, according to PipeLab. MCP servers need shared governance over content, credentials, and runtime trust because one weak link can affect the whole agent flow.
Editorial analysis by NHI Mgmt Group, based on content published by PipeLab: “The State of MCP Security 2026: Incidents, Attack Patterns, and Defense Coverage”.
By the numbers:
- 82% of 2,614 analyzed MCP implementations use file operations prone to path traversal.
- 67% use APIs related to code injection.
- The first publicly documented malicious MCP server, postmark-mcp, reached about 300 real organizations before disclosure.
Key questions
A: MCP can accelerate AI agent access to tools and data, but that also concentrates trust in a small set of configuration and credential paths.
Q: What are the signs that an MCP server has become a supply chain risk?
A: Look for packages that ship clean versions first, then change behaviour later, or for servers with broad workflow reach but weak review, provenance, and revocation.
Q: What breaks when MCP tools are treated as trusted by default?
A: When MCP tools are trusted by default, a poisoned or spoofed component can inherit privileged access, manipulate outputs, or expose secrets without crossing a traditional perimeter.
Practitioner guidance
- Audit MCP server inventory and ownership Identify every approved MCP server, who owns it, what data it can reach, and whether the approval path is still current.
- Scan tool definitions and responses at runtime Inspect descriptions, arguments, and returned content on every session so hidden instructions and injected data are visible before the agent acts.
- Validate file paths and command arguments strictly Reject escaping paths, canonicalise inputs before authorisation, and block any tool argument that can change the filesystem target or shell behaviour.
Bottom line: MCP creates a trust boundary problem where poisoned tool content, malicious servers, and exposed secrets can all steer agent behaviour.
Glossary terms: MCP tool poisoning, Delegated trust, Runtime Inspection, Shadow MCP Server
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
MCP security is becoming a delegated identity problem, not just a protocol problem. Once agents rely on third-party servers, package registries, and tool metadata, the attack surface includes trust assignment, not only transport and content. That shifts the core governance question from whether a tool is connected to whether it should ever be allowed to act with the same standing as a governed non-human identity. Practitioners should stop modelling MCP as a narrow integration layer and start modelling it as a runtime delegation boundary.
A few things that frame the scale:
- 28.65 million new hardcoded secrets were detected in public GitHub commits in 2025 alone, a 34% year-over-year increase and the largest single-year jump ever recorded, according to the State of Secrets Sprawl 2026.
- 96% of organisations store secrets outside of secrets managers in vulnerable locations including code, config files, and CI/CD tools, according to the Ultimate Guide to NHIs.
A question worth separating out:
Q: How should security teams decide between gateways, scanners, and runtime inspection for MCP?
A: Use gateways for routing and policy enforcement, scanners for pre-deploy review of tool definitions, and runtime inspection for poisoned content, arguments, and responses. None of the three covers the full attack surface on its own, so the decision is not either-or. It is which combination closes your most likely failure mode first.
👉 Read our full editorial: MCP security gaps span secrets, poisoning and runtime abuse