TL;DR: 121 agent components still use 100 high-risk domains in live configurations, Manifold Security found, including 108 skills, 11 MCP servers and 2 plugins. Agent workflows need pre-execution domain checks because a trusted endpoint can change payload, telemetry or persistence after publication.
Editorial analysis by NHI Mgmt Group, based on content published by Manifold Security: “The High-Risk Domains of Agent Skills and Where They Lead”.
By the numbers:
- The article says 121 agent components still use a high-risk domain for real.
- Finance skills make up 43% of the skills that use a high-risk domain, against 6% of all skills.
Key questions
Q: Why do high-risk domains in MCP and skill workflows create more than malware risk?
A: They create an access governance problem because the domain can control what code runs, what data leaves the host and whether the session leaves behind persistent state.
Q: How should security teams detect risky agent dependencies before they execute?
A: Use pre-execution checks against threat feeds, protective DNS and blocklists, then review the installer's actual network destinations and persistence behaviour.
Q: What breaks when an agent skill trusts a domain that later becomes malicious?
A: The trust model breaks because the agent executes a live dependency, not a static reference.
Practitioner guidance
- Audit every external domain in agent workflows Inventory the domains referenced in skills, MCP configs and plugins, then classify them as allowed, unknown or prohibited before any agent executes them.
- Preflight reputation checks before execution Check each referenced domain against protective DNS, threat feeds and malware filters before the component is loaded, not after the agent has connected.
- Block persistence from agent-installed tools Look for LaunchAgents, systemd user units and similar persistence mechanisms whenever a skill or installer changes host state.
Bottom line: Agent skills and plugins can smuggle in high-risk domains that control code execution, telemetry and persistence.
Glossary terms: Agent Dependency Graph, Integration Trust Debt, Persistent Host State, Pre-execution Reputation Check
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
Domain trust has become an identity control, not just a network control: In agent ecosystems, the URL inside a skill or plugin can determine what code runs, what data leaves the host and whether persistence is created. That means the security boundary is no longer the prompt alone. It is the dependency graph attached to the agent's execution path, and that boundary has to be governed before runtime, not investigated afterward.
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: What should teams do first when an agent workflow has already loaded a suspicious skill?
A: Contain the host state first. Check for installed services, scheduled persistence, unusual outbound connections and any machine identifiers already exposed, then revoke the workflow dependency and remove the component from approved use. That sequence matters because the risk may continue after the original session ends.
👉 Read our full editorial: High-risk domains in agent skills create hidden control gaps