←
Or Weis1,129 posts
Or Weis avatar

Or Weis

@OrWeis

Unrelenting entrepreneur Founder of @permit_io, @Rookoutlabs, @Reactful Permissions for the AI Era (Agent.security)

◷ Joined September 2013▧ 63 Photos and videos
Or Weis avatar
Or Weis@OrWeis·3h

The flag marks the client as an agent. It adds no scopes and doesn't decide which tool this agent may call for this user right now. That's still per-tool policy and an audit log. Full walkthrough: io.permit.io/gws-mcp-x

Or Weis avatar
Or Weis@OrWeis·3h

Clients still unmarked on Nov 12 stay non-agentic, so you may have to create a new one with the box ticked before you click Create. Then confirm with one harmless tool call, like listing calendars. Sign-in succeeding proves nothing here.

Or Weis avatar
Or Weis@OrWeis·3h

Find the client ID your MCP config actually uses. It is often not the client your REST app has used for years. If that client also backs non-agent features, leave it alone and create a separate agentic client for the agent.

Or Weis avatar
Or Weis@OrWeis·3h

Agents getting rejected by Google's hosted Workspace MCP servers since Nov 11? It's the OAuth client. User-delegated clients now need "Use this client for an AI-powered agent" selected, or Gmail, Drive, Calendar and the rest refuse the call. 🧵

Or Weis avatar
Or Weis@OrWeis·Nov 17

ABAC is the same middleware with richer data (department, invoice amount), and the limit lives in policy, not code. I ran this on Express 5.3.0, the permitio Node SDK 2.7.7 and @nodejs 24 against a stub PDP, with five passing tests: io.permit.io/express-authz-x

Or Weis avatar
Or Weis@OrWeis·Nov 17

Keep the middleware shape and move the decision to a PDP. With @permit_io that's permit.check(user, action, resource). The JWT identifies the user. Roles live in Permit per tenant. A revocation applies on the next check once it reaches the PDP. If the PDP is down, return 503.

Or Weis avatar
Or Weis@OrWeis·Nov 17

A hand-rolled RBAC map is fine until roles live in the token, the same person is admin in one tenant and viewer in another, the rule depends on data, or several services each keep a copy and they drift.

Or Weis avatar
Or Weis@OrWeis·Nov 17

First, auth middleware that verifies a JWT, pins the algorithm, and returns 401 when identity fails. 403 is for later, when you know who they are and the answer is no.

Or Weis avatar
Or Weis@OrWeis·Nov 17

Authorization in @expressjs is one decision per request: can this user perform this action on this resource? Express gives you the middleware hook. The decision is yours, and I walked through four steps with running code 🧵

Or Weis avatar
Or Weis@OrWeis·Nov 16

Both come down to control-plane authorization: who can create, rename, own and change adapters and tools, and what the gateway does with the values they supply. I put a checklist in the post: io.permit.io/mcp-gw-sec-x

Or Weis avatar
Or Weis@OrWeis·Nov 16

CVE-2026-125926 is an SSRF in mcp-gateway-registry's server registration and update API, disclosed by @awscloud. A user allowed to register or edit a server could point the upstream address at internal services. Versions 1.0.3 through 1.34.0 are affected. 1.35.0 fixes it.

Or Weis avatar
Or Weis@OrWeis·Nov 16

CVE-2026-109492 is a CWE-639 authorization bypass. @Microsoft scored it CVSS 8.8. User-chosen names became Kubernetes object names in one namespace, so a user who could create adapters or tools could take over another workload or the built-in tool gateway. Fixed in 1.0.0.

Or Weis avatar
Or Weis@OrWeis·Nov 16

Two CVEs in MCP gateways, both about who can change the gateway itself. I wrote up CVE-2026-109492 in the open-source @Microsoft MCP Gateway and CVE-2026-125926 in mcp-gateway-registry, disclosed by @awscloud. 🧵

Or Weis avatar
Or Weis@OrWeis·Nov 15

After the exchange you know who the user is. Whether their agent should call delete_customer_data after reading untrusted content gets decided per tool call. @zivxx wrote it up with a full validation checklist (code samples are schematic): io.permit.io/mcp-ema-x

Or Weis avatar
Or Weis@OrWeis·Nov 15

Claude-issued assertions find the user by email, so sign someone in only when that address or its domain is verified on your side. They're in beta, EMA needs a Claude Team or Enterprise plan, and @WorkOS MCP Auth added auto-connect in early access.

Or Weis avatar
Or Weis@OrWeis·Nov 15

aud has to equal your own issuer, and an aud array with more than one entry gets rejected even when one matches. Each jti is consumed once, atomically, in a shared store. If that store is down, reject the request.