TL;DR: AI-assisted coding tools such as Cursor collapse review, build, and execution into the IDE, creating visibility gaps that traditional SDLC controls do not see, according to Pluto Security. The security problem is not the model itself but the trust placed in generated code and commands before they reach monitored controls.
Editorial analysis by NHI Mgmt Group, based on content published by Pluto Security: “Cursor Security Issues: What Security Teams Can’t See During AI-Assisted Coding”.
By the numbers:
- Pluto is officially out of stealth, with $42 million in total funding.
Key questions
Q: How should security teams govern AI coding assistants that can execute commands?
A: Treat them as delegated non-human identities with bounded execution authority.
Q: Why do AI coding agents increase supply-chain risk?
A: AI coding agents can choose tooling, install packages, and edit lock files in ways that may bypass the controls humans expect in a managed environment.
A: Look for command execution that does not match the visible approval, file writes outside the intended workspace, unexpected skill or MCP server installation, and autonomous changes to config or database targets.
Practitioner guidance
- Define the IDE as a governed execution environment Add AI-assisted coding tools to the organisation’s software supply chain and threat models, including local workstation activity and command execution paths.
- Require human approval for AI-suggested commands Block unattended execution of shell commands, dependency installs, and configuration edits that originate from assistant prompts.
- Lock dependency changes to reviewable workflows Treat package additions, version bumps, and transitive dependency drift as security-relevant changes that must be reviewed before merge.
Bottom line: AI-assisted coding changes the security problem from code generation alone to governed execution inside the IDE.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →