
  <rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
      <title>Rambling Me</title>
      <link>https://www.rambling-me.com/blog</link>
      <description>A blog to reflect my thoughts, learnings, and observations</description>
      <language>en-us</language>
      <managingEditor>me@rambling-me.com (Dopeking)</managingEditor>
      <webMaster>me@rambling-me.com (Dopeking)</webMaster>
      <lastBuildDate>Tue, 08 Sep 2026 00:00:00 GMT</lastBuildDate>
      <atom:link href="https://www.rambling-me.com/tags/guardrails/feed.xml" rel="self" type="application/rss+xml"/>
      
  <item>
    <guid>https://www.rambling-me.com/blog/posts/technology/agentic/bounds-and-evidence/1-bounded-tools-not-free-form-access</guid>
    <title>Agentic Systems: Bounded Tools, Not Free-Form Access</title>
    <link>https://www.rambling-me.com/blog/posts/technology/agentic/bounds-and-evidence/1-bounded-tools-not-free-form-access</link>
    <description>Giving an agent a tool sounds like a scoping decision, and usually is not. A tool expressive enough to do everything is expressive enough to do the one thing you did not want, and no amount of instruction closes that gap. The case for bounding what an agent can express rather than checking what it produced, why bounded form does not imply bounded effect, and how to bound an agent whose output is prose.</description>
    <pubDate>Tue, 08 Sep 2026 00:00:00 GMT</pubDate>
    <author>me@rambling-me.com (Dopeking)</author>
    <category>technology</category><category>agentic</category><category>multi-agent-systems</category><category>guardrails</category><category>security</category><category>contracts</category><category>practitioner</category>
  </item>

    </channel>
  </rss>
