<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>MCP on Programmer.ie</title>
    <link>http://programmer.ie/tags/mcp/</link>
    <description>Recent content in MCP on Programmer.ie</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 08 Aug 2026 17:09:00 +0100</lastBuildDate>
    <atom:link href="http://programmer.ie/tags/mcp/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Capabilities and Routing</title>
      <link>http://programmer.ie/books/agents-from-first-principles/07-chapter/</link>
      <pubDate>Sat, 08 Aug 2026 17:09:00 +0100</pubDate>
      <guid>http://programmer.ie/books/agents-from-first-principles/07-chapter/</guid>
      <description>&lt;p&gt;Every mechanism built so far has taken the action set as given. The action boundary validates a proposal against a fixed list of permitted action types. Candidate generation samples several proposals from the same list. The runtime-state chapter watches what happens after execution and decides whether to continue. All of them assume that somebody, somewhere, already decided which capabilities the policy could choose from.&lt;/p&gt;&#xA;&lt;p&gt;Nobody did. That decision is the subject of this chapter, and it is a design decision with consequences as large as any of the mechanisms around it.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
