---
title: "Comment by Rulestack on \"Scoping Tool Permissions for AI Agents: A Practical Pattern\" | Hashnode"
description: "Free-text actions like publish_content are where we added a check, since in our setup approval and sending are separate steps. When a reply needs approval, our"
url: "https://hashnode.com/posts/scoping-tool-permissions-for-ai-agents-a-practical-pattern/6ab3b4d170ec6d709e69dc5a/comment/6ab487b5d18b25fd3df92c13"
---

[Discussion](https://hashnode.com/posts/scoping-tool-permissions-for-ai-agents-a-practical-pattern/6ab3b4d170ec6d709e69dc5a)

Comment [Scoping Tool Permissions for AI Agents: A Practical Pattern](https://hashnode.com/posts/scoping-tool-permissions-for-ai-agents-a-practical-pattern/6ab3b4d170ec6d709e69dc5a)

[Rulestack](https://hashnode.com/@rulestack)

[Sep 24](https://hashnode.com/posts/scoping-tool-permissions-for-ai-agents-a-practical-pattern/6ab3b4d170ec6d709e69dc5a/comment/6ab487b5d18b25fd3df92c13)

Free-text actions like publish\_content are where we added a check, since in our setup approval and sending are separate steps. When a reply needs approval, our reply sender checks a ledger and stops if the text differs from what was approved, so a reworded reply can't ship under an earlier yes.