[Openid-specs-authzen] Fwd: [modelcontextprotocol/modelcontextprotocol] Spec Proposal: A Gateway-Based Authorization Model (Discussion #804)

David Brossard david.brossard at gmail.com
Thu Mar 12 09:09:58 UTC 2026


Interesting comment re. MCP and authorization

---------- Forwarded message ---------
From: policylayer-dan <notifications at github.com>
Date: Tue, Mar 10, 2026 at 10:52 PM
Subject: Re: [modelcontextprotocol/modelcontextprotocol] Spec Proposal: A
Gateway-Based Authorization Model (Discussion #804)
To: modelcontextprotocol/modelcontextprotocol <
modelcontextprotocol at noreply.github.com>
Cc: David Brossard <david.brossard at gmail.com>, Comment <
comment at noreply.github.com>


Great proposal. We've built a working open-source implementation of this
pattern — Intercept <https://github.com/PolicyLayer/Intercept> is a
transparent MCP proxy that evaluates every tools/call request against
YAML-defined policies before forwarding to the upstream server.

It addresses several of the problems outlined here:

   - *Fine-grained per-request enforcement*: Each tool call is evaluated
   against rules that can check tool name, argument values, and stateful
   counters (rate limits, spend caps). This gives you the "checkpoints for
   each subsequent action" the proposal describes.
   - *No client-side changes*: The agent connects to Intercept like any MCP
   server. It doesn't know the proxy is there.
   - *Deterministic policy*: Rules are YAML, evaluated at the transport
   layer — below the model context. The agent can't reason around them.
   - *Works today*: npx -y @policylayer/intercept -c policy.yaml --
   <server-command> wraps any stdio MCP server.

Would be interested in how the spec could formally accommodate per-request
policy enforcement, whether as part of the gateway model or as a standalone
extension.

https://github.com/PolicyLayer/Intercept

—
Reply to this email directly, view it on GitHub
<https://github.com/modelcontextprotocol/modelcontextprotocol/discussions/804#discussioncomment-16074642>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABPRFP6SMDRSYSO55E7WMFD4QCFB3AVCNFSM6AAAAAB7XNY53KVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTMMBXGQ3DIMQ>
.
You are receiving this because you commented.Message ID:
<modelcontextprotocol/modelcontextprotocol/repo-discussions/804/comments/16074642
@github.com>


-- 
---
David Brossard
http://www.linkedin.com/in/davidbrossard
http://twitter.com/davidjbrossard
http://about.me/brossard
---
Stay safe on the Internet: IC3 Prevention Tips
<https://www.capefearnetworks.com/wp-content/uploads/2017/05/Internet-Fraud-Prevention-Tips-IC3.pdf>
Prenez vos précautions sur Internet:
https://cyber.gouv.fr/bonnes-pratiques-protegez-vous
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-authzen/attachments/20260312/4b9a5582/attachment-0001.htm>


More information about the Openid-specs-authzen mailing list