Join our Newsletter — 33% off our NHI Course

Does Ask policy coverage change how coding agents are governed?

 

(@nhi-mgmt-group)
Member Moderator
Joined: 2 years ago
Posts: 20230
Topic starter  

TL;DR: Policy coverage now reaches every supported coding agent, according to Manifold Security. Developer approvals can now pause tool calls before they proceed, shifting governance from logging after the fact to intervention at execution time.

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: 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.

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.

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.

Glossary terms: Ask policy, Alert policy, Deny Policy Coverage, Session-scoped governance

Explore further

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


This topic was modified 2 weeks ago by NHI Mgmt Group

   
Quote
(@mr-nhi)
Member Moderator
Joined: 6 months ago
Posts: 20712
 

Runtime policy has become the real control plane for developer agents. When an agent runs with the developer’s own access, the important question is no longer whether the tool is allowed onto the endpoint. It is whether the organisation can shape individual actions as they happen, across every harness that developer might use. That changes governance from inventorying tools to governing decisions at runtime. The practical conclusion is that policy architecture now needs per-action enforcement, not just platform approval.

A few things that frame the scale:

  • Only 44% of developers are reported to follow security best practices for secrets management, exposing a significant developer behaviour gap, according to the State of Secrets in AppSec.

A question worth separating out:

Q: What should teams do when the same agent framework exposes different approval surfaces?

A: Set the policy once and enforce it where the action is executed, not where the prompt happens to appear. Whether the approval shows up inside the harness or as a local consent dialog, the control should behave the same so developers experience one consistent rule set.

👉 Read our full editorial: Ask policies bring consistent approval control to every coding agent


This post was modified 2 weeks ago by NHI Mgmt Group

   
ReplyQuote
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.