Join our Newsletter — 33% off our NHI Course

Did scanners miss malicious MCP server behavior at runtime?

 

(@nhi-mgmt-group)
Member Moderator
Joined: 2 years ago
Posts: 20217
Topic starter  

TL;DR: Public MCP scanners returned clean or zero-finding results against malicious servers, Pluto Security found after testing five scanners. MCP checks are only meaningful when they cover metadata, source, and runtime behavior, not just a narrow slice of evidence.

Editorial analysis by NHI Mgmt Group, based on content published by Pluto Security: “Malicious Servers, Clean Scans: The Dangerous Illusion of a Clean MCP Scan”.

Key questions

Q: Why does incomplete MCP scanning create false confidence?

A: Because the result reflects the evidence the scanner actually saw, not the whole server.

Q: How should teams evaluate an MCP server before production use?

A: Check maintainer identity, documentation quality, update recency, and dependency posture, then validate that the client can be limited to specific tools and actions.

Q: What breaks when an MCP scanner only checks metadata?

A: It misses the server’s real behavior at tool-call time.

Practitioner guidance

  • Validate scan coverage before trusting results Record whether the scanner inspected metadata, source files, dependency context, tool output, and runtime behavior.
  • Test unknown MCP servers in isolation Run new servers in a sandbox with fake credentials, a temporary home directory, and restricted network access so you can observe what they touch when tools are called.
  • Pin and review the exact server version Track the commit, package hash, and update path for every server you allow, because behavior can change after installation even when the tool name stays the same.

Bottom line: MCP scanners can miss malicious behavior when they inspect only metadata or an incomplete slice of source code.

Glossary terms: MCP scanner, Runtime Trust, Scan coverage, Malicious MCP Server

Explore further

View Full Forum →  |  NHI Foundation Course →  |  Our Services →  |  Read the full analysis →


This topic was modified 1 week ago by NHI Mgmt Group

   
Quote
(@mr-nhi)
Member Moderator
Joined: 6 months ago
Posts: 20707
 

Clean scan results do not establish runtime trust for MCP servers. The scanner may have reviewed tool names, descriptions, or partial source, but MCP risk lives in what the server actually does when an agent invokes it. That gap is structural, not cosmetic. Security teams need to stop treating a zero-finding result as a trust decision and start treating it as one input into a broader review of runtime behavior.

A few things that frame the scale:

  • 24,008 unique secrets were exposed in MCP configuration files in 2025 alone, the protocol's first year of widespread adoption, according to the State of Secrets Sprawl 2026.

A question worth separating out:

Q: How do you know an MCP server scan is actually meaningful?

A: You know it is meaningful only when you can state exactly what the scanner covered and what it could not cover. A result that includes metadata but excludes source, runtime behavior, or oversized files cannot answer the full trust question. The useful question is coverage, not the badge on the result.

👉 Read our full editorial: Clean MCP scans can miss malicious runtime behavior


This post was modified 1 week ago by NHI Mgmt Group

   
ReplyQuote
Share:

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.