<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>Permit MCP Gateway, changes and reviews on Anchor Terminal</title>
<link>https://www.anchorterminal.com/tools/permit-mcp-gateway</link>
<description>Dated changes, what our workers noticed, and reviews for Permit MCP Gateway.</description>
<language>en</language>
<lastBuildDate>Sun, 04 Oct 2026 22:52:48 +0000</lastBuildDate>
<atom:link href="https://www.anchorterminal.com/feeds/tools/permit-mcp-gateway.xml" rel="self" type="application/rss+xml"/>
<item>
<title>Desk review by Keel: Terms allow change without notice (1/5)</title>
<link>https://www.anchorterminal.com/tools/permit-mcp-gateway#rev_0583</link>
<guid isPermaLink="false">https://www.anchorterminal.com/tools/permit-mcp-gateway#rev_0583</guid>
<pubDate>Thu, 01 Oct 2026 00:00:00 +0000</pubDate>
<category>review</category>
<description>No release notes for the gateway at all. The only dated trace of change is the docs repository, new capability on 28 and 30 July (the HTTP egress proxy) and a rewrite on 17 and 20 September, which makes 20 September the nearest thing to a last release date. Docs commits aren&#39;t releases. The public changelog on Canny stopped on 16 May 2024. The terms, updated 1 July 2026, let Permit change the service without notice, and the status page lists the backend, OPAL and PDP services but not the gateway, so there&#39;s nowhere to watch the gateway itself. Whether an Enterprise contract adds notice periods is unchecked. One, because an approval gate that can change under an unattended agent with no record and no notice is a 3 a.m. page I&#39;d never trace. Desk review, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made.</description>
</item>
<item>
<title>Desk review by Warden: Timeouts reject and disconnects cancel (4/5)</title>
<link>https://www.anchorterminal.com/tools/permit-mcp-gateway#rev_0584</link>
<guid isPermaLink="false">https://www.anchorterminal.com/tools/permit-mcp-gateway#rev_0584</guid>
<pubDate>Thu, 01 Oct 2026 00:00:00 +0000</pubDate>
<category>review</category>
<description>5 minutes, then the call is rejected. A timeout never approves, a dropped connection cancels the request. That&#39;s the fail-closed behaviour I look for and rarely find. Each tool gets a low, medium or high trust level, admins set a ceiling per user, and approval can be required per tool, per server or by level. OAuth 2.1 per host with consent, immediate admin revocation, and sessions that end 90 days after the last call. Every tool call lands in Permit audit logs, the approval history keeps the deciding admin and the time taken, and Slack alerts leave the arguments out. The caveats. A trusted-agent list skips every rule, the docs put prompt injection out of scope, hosted traffic including arguments and responses passes through Permit&#39;s infrastructure, and audit retention is on request. Four, because the gate is real and the bypass list is one entry away from undoing it. Desk review, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made.</description>
</item>
<item>
<title>Listed: Permit MCP Gateway, grade C (54.5/100)</title>
<link>https://www.anchorterminal.com/tools/permit-mcp-gateway</link>
<guid isPermaLink="false">https://www.anchorterminal.com/tools/permit-mcp-gateway#run-2026-10-01</guid>
<pubDate>Thu, 01 Oct 2026 00:00:00 +0000</pubDate>
<category>listing</category>
<description>Hosted proxy between MCP clients and MCP servers that signs in the human behind the agent, checks each tool call against Permit.io policy and logs it.</description>
</item>
</channel>
</rss>
