Tagged “mcp”

4 posts · View all tags
Give each MCP tool its own scope, and return a refusal the client can act on
IntermediatePart 10

Give each MCP tool its own scope, and return a refusal the client can act on

Part 6 gated the whole server with one scope, which meant the token that let an agent look up a customer also let it issue refunds. Splitting that per tool is easy. Making the refusal useful is not: the obvious implementation returns HTTP 200 with the error buried in the body, so a client has nothing to trigger step-up authorization on. Getting the 403 and WWW-Authenticate challenge the spec defines means leaving the framework's abstraction entirely — and the version that does it decodes the token a second time, unverified.

Agentsself-hostingmcpsecurity
September 18, 202612 min read
Read more
The wrong valid token: authenticating an MCP tools server with authentik
IntermediatePart 6

The wrong valid token: authenticating an MCP tools server with authentik

Agent orchestration part 4 scoped tools in the client and admitted the server still trusted whoever reached the port. This puts a JWT verifier in front of it, with its own authentik client, so the tools server refuses anonymous callers — and refuses the gateway's own valid token, because a separate provider means a separate issuer. Includes the documented client-credentials helper that cannot work here, and the four silent 404s it produces instead of saying so.

Agentsself-hostingmcpsecurity
September 10, 202616 min read
Read more
Split one MCP toolbox between two agents so the scheduler cannot issue refunds
IntermediatePart 4

Split one MCP toolbox between two agents so the scheduler cannot issue refunds

Part 3 handed one agent all five tools and let a human pause guard the dangerous one. That guard depends on the model asking. This splits the same MCP server between a scheduler and a billing agent, so the scheduler cannot refund an invoice for the simplest reason available — the tool was never in its list. Then the supervisor goes back on top, and routing turns out not to be the guarantee.

AIAgentsself-hostingmcp
September 4, 202613 min read
Read more
Book appointments and refund invoices from a LangGraph agent over MCP
IntermediatePart 3

Book appointments and refund invoices from a LangGraph agent over MCP

The scheduler and billing agents from Parts 1 and 2 never actually scheduled or billed anything. This gives them a calendar, a customer list and a refund that no model can issue alone — over MCP, on the stateless spec, with the model on WEC Inference. Includes three things nobody documents: your server still defaults to sessions, ctx.elicit is the old API and its era error goes to the model, not to you, and cache=True does nothing unless the server advertises a TTL.

AIAgentsself-hostingmcp
September 3, 202621 min read
Read more