Project Templates์ถœ์ฒ˜: Show HN์กฐํšŒ์ˆ˜ 13

Show HN: Pincer-MCP โ€“ Stop AI agents from reading their own credentials

By why_prem
2026๋…„ 2์›” 10์ผ
**Show HN: Pincer-MCP โ€“ Stop AI agents from reading their own credentials**

I run AI agents for coding (OpenClaw, Claude Desktop) and realized they could read their own .env files. Tested it - asked my agent to "check configuration" and it printed everything.The problem: agents need file access to work, but if they can read files, they can read their own credentials. One prompt injection and your API keys are leaked.Standard solutions don't help: - Environment variables: agent can read process.env - Secret managers: agent needs credentials to access them - Better prompting: can't security-patch an LLM with instructionsI built a proxy token architecture instead. The agent never sees real credentials:- Agent has: pxr_abc123 (proxy token) - Real keys: encrypted in OS keychain - On API call: decrypt key, make call, scrub memory immediatelyBuilt in 1 week. 500 npm installs with zero promotion (people are searching for this).GitHub: https://github.com/VouchlyAI/Pincer-MCP npm: npm install -g pincer-mcpWorks with OpenClaw, Claude Desktop, any MCP client.Looking for security feedback - if you see holes in the architecture, please tell me...

---

**[devsupporter ํ•ด์„ค]**

์ด ๊ธฐ์‚ฌ๋Š” Show HN์—์„œ ์ œ๊ณตํ•˜๋Š” ์ตœ์‹  ๊ฐœ๋ฐœ ๋™ํ–ฅ์ž…๋‹ˆ๋‹ค. ๊ด€๋ จ ๋„๊ตฌ๋‚˜ ๊ธฐ์ˆ ์— ๋Œ€ํ•ด ๋” ์•Œ์•„๋ณด์‹œ๋ ค๋ฉด ์›๋ณธ ๋งํฌ๋ฅผ ์ฐธ๊ณ ํ•˜์„ธ์š”.