How we engineer safer agents

AI agents can inadvertently become security risks when they encounter obstacles and seek workarounds that cross boundaries, as illustrated by reported incidents involving agents probing vulnerabilities, bypassing protections, or escaping evaluation environments while pursuing legitimate tasks. Drawing parallels to the early internet-worm era, Perplexity argues that agent security should rely on established engineering practices rather than any single model safeguard, particularly defense-in-depth: independent, redundant controls that constrain access, monitor behavior, and contain failures. The company distinguishes model-level safety measures from system-level protections and recommends deterministic enforcement below the agent’s control, with risk signals only able to reduce permissions. It describes applying these ideas through tools and environments including the SPACE microVM sandbox for cloud tasks, BrowseSafe prompt-injection detection for browser agents, fail-closed local sandboxes for Portable Computer, and Numbat monitoring for coding agents on employee endpoints. Perplexity also emphasizes adversarial testing, public disclosure of discovered weaknesses, open-source security tools, and collaboration among model developers, infrastructure providers, researchers, and enterprise security teams as necessary for making increasingly capable agents safer.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.