Back to News
Advertisement
bb4timer about 4 hours ago 2 commentsRead Article on github.com

ES version is available. Content is displayed in original English for accuracy.

Hey HN, Adam here.

We built a small MCP example around a single problem:

How do you let an agent use a tool that needs credentials without giving the credentials to the agent?

The demo has two tools. One is open. One is protected.

When the agent calls the protected tool, Keydris checks the policy first:

ALLOW → run the tool REJECT → stop

The credential stays on the server. The agent never sees it.

We do the check through a small middleware on the MCP server called the KIT Reader.

Repo: https://github.com/keydrisLabs/mcp-auth-keydris-template

We're early. If you're building with MCP, Claude Code or Codex, I'd love to know how you're handling this today and where you think this approach breaks.

We support other elements like integrations etc but would love your feedback

Advertisement

Discussion (2 Comments)Read Original on HackerNews

evanjrowleyabout 3 hours ago
How would someone send the audit evidence to their organization's centralized log collection service(s)?
Maxious8 minutes ago
Other MCP gateway platforms seem to send extensive records to SIEM systems https://docs.domesystems.ai/operate