<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Topics tagged with mcp]]></title><description><![CDATA[A list of topics that have been tagged with mcp]]></description><link>https://xcp-ng.org/forum/tags/mcp</link><generator>RSS for Node</generator><lastBuildDate>Thu, 30 Jul 2026 21:09:23 GMT</lastBuildDate><atom:link href="https://xcp-ng.org/forum/tags/mcp.rss" rel="self" type="application/rss+xml"/><pubDate>Thu, 30 Jul 2026 18:39:34 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[XO 6.7 REST API - full coverage for MCP agents, updated same day (267 tools, open source)]]></title><description><![CDATA[Congrats on getting this out so fast after 6.7, and thanks for the writeup, genuinely interesting approach. The declarative angle instead of wrapper code per endpoint makes sense to me, especially given how often the REST surface grows.
One thing I keep wondering about: you framed the auth/audit/fail-closed checks as sitting in front of the gateway. What happens when the model actually asks for something destructive, a VDI delete, a host disable, that kind of thing? Does the gateway block it outright, or does a human need to sign off somewhere in there?
I'm asking because that's close to the exact boundary question our own Insights piece touched on this month. I'm community manager here, not a developer, so I'd rather ask than guess at how the security model actually behaves. Want to understand it properly before I say more.
Passing this along internally too. No promises on timing, but it's the kind of thing worth a closer look.
]]></description><link>https://xcp-ng.org/forum/topic/12391/xo-6.7-rest-api-full-coverage-for-mcp-agents-updated-same-day-267-tools-open-source</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/12391/xo-6.7-rest-api-full-coverage-for-mcp-agents-updated-same-day-267-tools-open-source</guid><dc:creator><![CDATA[poddingue]]></dc:creator><pubDate>Thu, 30 Jul 2026 18:39:34 GMT</pubDate></item></channel></rss>