One in four MCP servers opens AI agent security to code execution risk
Noma Security whitepaper finds most popular AI Skills and many MCP servers carry high-risk capabilities, with state changes most prevalent.
Noma Security analyzed hundreds of popular MCP servers and Skills across eight risk categories, finding most widely used Skills carry at least one risky characteristic and a typical enterprise runs well over a hundred high-risk agent tools, with arbitrary code execution common across MCP servers. The most prevalent risk is the ability to change state or data, and named toxic combinations include ContextCrush data leakage, ForcedLeak via poisoned Salesforce CRM records, DockerDash supply-chain compromise, the Replit production database deletion, and the hijacked Amazon Q VS Code extension. Building on OWASP LLM06:2025, the paper proposes the No Excessive CAP framework of capabilities, autonomy, and permissions, recommending allowlisting, MCP version pinning, approval gates on irreversible actions, and user-scoped expiring credentials.
AIR raises $50M to help companies vet the skills and add-ons AI agents use
AI security startup AIR exits stealth with $50M across two seed rounds to continuously vet skills, plugins, and MCP servers used by enterprise AI agents.
AIR, founded by Unit 8200 veterans Yair Saban and Niv Hoffman, raised $10 million led by Sequoia and $40 million led by Greenoaks to secure the emerging AI agent software supply chain. Its platform discovers agents in enterprise environments, intercepts their actions, and continuously vets skills, add-ons, and MCP servers against a maintained whitelist, filtering out about 27% of found add-ons. The company claims over 20 customers, roughly a quarter large enterprises, with strong demand in financial services and pharma, and competes with Noma Security, Zenity, Astrix Security, and Operant AI.
AI workflows may be creating a dangerous new authorization blind spot
Noma Labs researchers describe 'workflow identity hijacking,' letting unauthenticated users trigger privileged AI workflows that execute actions with high-privilege service accounts.
Noma Labs lead researcher Sasi Levi detailed 'workflow identity hijacking,' where benign unauthenticated inputs via support inboxes, GitHub issues, or web forms trigger enterprise AI pipelines that execute privileged actions. The workflow runs using high-privilege service accounts or developer API keys, decoupled from the requester's identity, effectively creating a confused-deputy condition. Unlike prompt injection, the model behaves correctly; the failure lies in authorization enforcement at the workflow layer, and activity blends into routine automation. Mitigations include identity-aware access at execution points and user-context propagation between AI outputs and downstream operations.
New AI Workflow Identity Hijacking Attack Lets Hackers Exfiltrate Sensitive Data
Noma Labs disclosed Workflow Identity Hijacking, an AI automation flaw letting anonymous users trigger privileged data exfiltration without prompt injection or stolen credentials.
Noma Labs researcher Sasi Levi described Workflow Identity Hijacking, where AI workflows process untrusted input from low-privileged or anonymous users but execute downstream actions with the workflow creator's elevated permissions, turning the pipeline into an unauthenticated proxy. Unlike prompt injection, the model is not tricked; the flaw is a missing authorization check between the requester and the privileged actions. Noma Labs also disclosed and helped fix a similar issue in Google Workflows, and linked the problem to the earlier GitLost research on GitHub Agentic Workflows. Recommended mitigations include per-user identity propagation, least-privilege service accounts and authorization checks before every downstream action.