Join our Newsletter — 33% off our NHI Course

Ask policies for coding agents: what changes for developer workflows?

 

(@nhi-mgmt-group)
Member Moderator
Joined: 1 year ago
Posts: 18346
Topic starter  

TL;DR: An Ask policy now reaches every supported coding agent, according to Manifold Security, so a developer approval can pause a tool call instead of letting it proceed or only logging it. The shift matters because security teams can tune policy intent first, then decide which actions should stop, which should ask, and which should simply record.

Editorial analysis by NHI Mgmt Group, based on content published by Manifold Security: “Blocking Is the Only Answer Most Security Tools Have. "Ask" Lets the Developer Decide.”.

Key questions

Q: How should security teams roll out policy controls for coding agents without blocking legitimate work?

A: Start with Alert so you can measure what the rule actually catches, then promote only the actions that clearly need human approval or outright denial.

Q: What breaks when a policy only logs agent activity instead of pausing the action?

A: Logging alone cannot stop a sensitive action from completing, so the control arrives after the risk has already materialised.

Q: Why do developer agents need approval at the action level instead of the session level?

A: Because a session can contain both harmless and risky steps, and the risky one may appear halfway through a routine task.

Practitioner guidance

  • Define three policy outcomes by action type Use Ask for actions that need human judgement, Alert for actions you want to observe first, and Deny only for a short list of clearly unsafe actions.
  • Run new policies in Alert before enforcement Use a monitoring period to measure real hit rates, identify which developers are touched, and separate legitimate friction from unacceptable behaviour.
  • Classify sensitive file reads as review-worthy actions Treat reads of credential files, tokens, and similar secrets as distinct governance events rather than as ordinary file access inside the agent session.

Bottom line: The article shows that agent governance is shifting from post-event visibility to per-action intervention at the point of execution.

Explore further

View Full Forum →  |  NHI Foundation Course →  |  Our Services →  |  Read the full analysis →



   
Quote
Share:

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.