<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>RAR on Control Plane by Karl McGuinness</title><link>https://notes.karlmcguinness.com/tags/rar/</link><description>Recent content in RAR on Control Plane by Karl McGuinness</description><generator>Hugo</generator><language>en-us</language><managingEditor>public@karlmcguinness.com (Karl McGuinness)</managingEditor><webMaster>public@karlmcguinness.com (Karl McGuinness)</webMaster><lastBuildDate>Tue, 02 Jun 2026 10:00:00 -0700</lastBuildDate><atom:link href="https://notes.karlmcguinness.com/tags/rar/index.xml" rel="self" type="application/rss+xml"/><item><title>Least-Privilege MCP Tool Calls Need a Mission</title><link>https://notes.karlmcguinness.com/notes/least-privilege-mcp-tool-calls/</link><pubDate>Tue, 02 Jun 2026 10:00:00 -0700</pubDate><author>public@karlmcguinness.com (Karl McGuinness)</author><guid>https://notes.karlmcguinness.com/notes/least-privilege-mcp-tool-calls/</guid><description>Least-privilege MCP has two natural authorization paths: token-side FGA with PRM, RAR, and RAR-type metadata, or resource-side FGA with the MCP server as PEP and AuthZEN as PDP. The token-side path gives the client portable authority but forces each AS to understand resource-domain semantics. The resource-side path keeps domain knowledge at the MCP server but fragments approvals and audit across PDPs. Both need a durable task object. A Mission lets the originating AS own the user-approved task while each Resource Server enforces with its own domain knowledge.</description></item></channel></rss>