Skip to main content
Search

# AI Agent Security

2 related articles

Subscribe to updates
  1. arXiv

    Tool descriptions become security contracts: 253 bugs in 273 MCP servers, most without a crash

    When a large language model calls an external tool, the orchestration layer checks that the call is well formed, not that its arguments are safe. ToFu turns the argument semantics already documented in tool metadata into executable security checks, then generates fuzzing inputs and oracles from them, confirming 253 bugs across 343 tools in 118 of 273 runnable MCP servers, most of which returned normally.

  2. NVIDIA Research

    AI Security Is an Engineering Problem: Solving It at Every Layer of the Agent Stack

    This article argues that AI security should be treated as an engineering problem requiring defined security requirements, enforceable controls, named owners, and evidence that protections work, and proposes that security depends on the full agent stack (models, harnesses, runtime environments) working together, introducing NVIDIA OpenShell as an open source secure runtime with integrations across Open Secure AI Alliance partners, along with defensive tool examples such as CrowdStrike SafeMind, Palo Alto Networks Prisma AIRS, Capital One VulnHunter, and ReversingLabs Spectra Assure, while emphasizing open sharing of failure evidence and verification methods to shift advantage toward defenders.

You’re all caught up