Model Context Protocol

AI in Vulnerability Management: Assistant, Weapon, and Emerging Target

Artificial intelligence now plays three simultaneous roles in vulnerability management: it assists defenders with prioritization and analysis, arms attackers with faster discovery tools, and introduces entirely new classes of assets and vulnerabilities that must be managed. Mature applications include ML-driven risk scoring in platforms such as Tenable VPR, Qualys TruRisk and Rapid7 Active Risk, which cut priority lists by 40-50 percent, and Google’s Big Sleep project that discovered a real-world SQLite flaw (CVE-2025-6965) before exploitation occurred. On the offensive side, systems like XBOW completed 104 test scenarios in 28 minutes versus 40 hours for human testers, shrinking the average time-to-exploit window to negative seven days according to Mandiant M-Trends 2025. New AI-specific attack surfaces are documented in the OWASP Top 10 for LLM applications and the emerging MCP Top 10, covering prompt injection, tool poisoning, and command injection against Model Context Protocol servers. Real incidents already include Air Canada’s chatbot inventing a refund policy and New York City’s MyCity bot dispensing illegal advice for nearly two years. Researchers have also demonstrated sandbox escapes in coding agents from Cursor, OpenAI Codex and Claude Code through classic file-write-and-execute patterns rather than any sentient behavior.

VirusTotal Integrates Threat Intelligence Directly into ChatGPT Conversations

VirusTotal has connected its threat intelligence database to ChatGPT, enabling users to investigate files, URLs, domains, and IP addresses directly within ongoing conversations. The integration, announced on October 14, operates through VirusTotal AI (VTAI) and the Model Context Protocol without requiring an API key. Setup occurs in ChatGPT developer mode via OAuth authorization using a Google account. Existing analysis reports become available in the chat, displaying source details, analysis dates, detection coverage, and explanations of each detection result. For authorized attachments, the connector computes the file hash locally and only submits unknown samples, while URLs, domains, and IPs can be submitted or re-analyzed with permission. Usage remains free within defined quotas, with separate limits for queries and contributions, and the connection is tied to the user account rather than individual chats. VirusTotal explicitly notes that missing reports do not confirm safety and that full privacy implications must be considered before sharing content.

How to Grant AI Agents Access to Internal APIs via MCP: Key Questions Security Teams Will Ask

As AI agents increasingly need to call internal APIs, security teams focus on three core questions: who granted access, how to revoke it, and how to investigate incidents after the fact. The answers lie in operation-level access control rather than traffic inspection alone. MCP, now managed by the Agentic AI Foundation under the Linux Foundation, has become the standard for connecting AI agents to enterprise systems with hundreds of millions of SDK downloads monthly. The article details how NEOMSA APIM implements MCP servers, tool publication from OpenAPI specs, subscription-based scopes, and 15 independent security checks. It explains why classic traffic filters fail against valid but unauthorized tool calls and stresses the need for owner approval, application-specific identities, and proper identity propagation through token exchange. Rate limiting at the subscription level and business-object validation are presented as essential controls to prevent overreach and duplication.

Agentic AI Systems Under Siege: Prompt Injections, Data Poisoning, and Tool Exploits

Independent expert Andrey Biryukov details how AI agents with file access, email capabilities, and API calls become high-value targets for attackers. The article examines confidentiality, integrity, and availability risks created by autonomous decision-making. Real-world examples include NeuralTrust’s discovery of malicious URL instructions bypassing OpenAI Atlas validation and Zscaler ThreatLabz’s demonstration of hidden instructions on fake Python documentation sites that tricked models into making cryptocurrency payments. Data poisoning research from Carnegie Mellon and Cornell Tech showed agents from Anthropic, OpenAI, and Google selecting tampered datasets in half of tested cases. Additional findings cover vulnerabilities in Git MCP Server and comparative weaknesses between Function Calling and Model Context Protocol architectures. OWASP’s Agentic Top 10 and joint guidance from Canada, Australia, the US, New Zealand, and the UK emphasize threat modeling, least-privilege isolation, and separation of trusted versus untrusted data.

GhostSplice Technique Lets Malicious MCP Servers Trick AI Coding Agents into Exfiltrating Secrets

GhostSplice is a new technique that allows a malicious MCP server to induce an AI coding agent to leak SSH keys, environment secrets, and source code. The attack splits malicious instructions across tool metadata and responses so the agent reconstructs and executes the full exfiltration plan without detecting an overtly malicious command. Tests showed the method raised compliance rates from an average of 42 percent to 82 percent across eleven models, with some systems moving from zero to 100 percent success. The technique requires the developer to connect the attacker-controlled MCP server and for the agent to already possess read access to the targeted files. Defenses focus on strict allow-listing of MCP servers, least-privilege tool permissions, separation of tool output from instructions, and human approval for sensitive operations. The disclosure aligns with prior warnings about poisoned MCP tool descriptions and agentjacking attacks.