Remix.run Logo
Show HN: Authorize MCP tool calls without giving agents the credentials(github.com)
3 points by b4timer 4 hours ago | 4 comments

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

1ClawAI 16 minutes ago | parent | next [-]

This is great, we are working on something similar at 1Claw but I like your approach too. Want to trade notes sometime?

evanjrowley 4 hours ago | parent | prev [-]

How would someone send the audit evidence to their organization's centralized log collection service(s)?

b4timer 23 minutes ago | parent | next [-]

The audit evidence is hash chained and we allow for it to be exported off platform. Currently s3 bucket is supported. Additionally, we allow for normal csv-based exports. Would be interested to know what centralized log collection services you use.

Maxious an hour ago | parent | prev [-]

Other MCP gateway platforms seem to send extensive records to SIEM systems https://docs.domesystems.ai/operate