---
title: "Comment by Kartik N V J K on \"The OWASP LLM Top 10 2026 Is Not a Vulnerability List. It's a Blast Radius Document\" | Hashnode"
description: "Excessive Agency climbing to number three matches what I'm seeing, the risk moved from what the model says to what it's allowed to do. Blast radius is the right"
url: "https://hashnode.com/posts/owasp-llm-top-10-2026-blast-radius/6a8c0a3a6401eecbc70af341/comment/6a8c893b6a595f21d5ff48cc"
---

[Discussion](https://hashnode.com/posts/owasp-llm-top-10-2026-blast-radius/6a8c0a3a6401eecbc70af341)

Comment [The OWASP LLM Top 10 2026 Is Not a Vulnerability List. It's a Blast Radius Document](https://hashnode.com/posts/owasp-llm-top-10-2026-blast-radius/6a8c0a3a6401eecbc70af341)

[Kartik N V J K](https://hashnode.com/@kartik-nvj)

[Aug 24](https://hashnode.com/posts/owasp-llm-top-10-2026-blast-radius/6a8c0a3a6401eecbc70af341/comment/6a8c893b6a595f21d5ff48cc)

Excessive Agency climbing to number three matches what I'm seeing, the risk moved from what the model says to what it's allowed to do. Blast radius is the right lens, a wrong answer is cheap but a wrong action with tool access is not. How are you scoping agent permissions to keep that radius small?

[Mohit Kumar](https://hashnode.com/@mkd)

[Aug 26](https://hashnode.com/posts/owasp-llm-top-10-2026-blast-radius/6a8c0a3a6401eecbc70af341/comment/6a8c893b6a595f21d5ff48cc#reply-6a8e6950345f80f6e33ee1cd)

Exactly! That's how I see it too. A wrong answer is often recoverable; a wrong action with access to real systems can have a very different impact. For permissions, I'm leaning toward treating the agent's capabilities as an explicit graph and looking at the possible tool combinations rather than evaluating each permission in isolation. The goal is to keep the agent's reachable blast radius as small as possible for the task it's actually supposed to perform. That's also something I'm exploring more deeply in my work on agent security.
