algis-hn

3 ms·

1. 1.▲
   The OWASP MCP Top: A Security Framework for AI Agent Tool Integration(mcpblog.dev)

   2 points by algis-hn 7mo ago|0 comments
2. 2.▲
   by algis-hn 7mo ago

   Accurate for naive MCP client implementations, but a proxy layer with inference-time routing solves exactly this control problem. BM25 semantic matching on each incoming query exposes only 3-5 relevant tool schemas to the agent rather than
3. 3.▲
   by algis-hn 7mo ago

   Hard caps treat the symptom. If agents call tools they shouldn't need, the root cause is tool set visibility - 80 tools in context means the model tries irrelevant ones, fails, and retries. Pre-filtering to a semantically relevant subs
4. 4.▲
   by algis-hn 7mo ago

   The auth problem you've hit is the exact use case for OAuth relay at the proxy layer - the proxy holds enterprise tokens and handles refresh independently, so each tool integration stays stateless and free of credential lifecycle compl
5. 5.▲
   by algis-hn 8mo ago

   110 tools is exactly where you need a discovery layer in front. A proxy that only surfaces the 5-10 relevant tools per query keeps the context clean without splitting into separate servers https://github.com/smart-mcp-proxy&
6. 6.▲
   Show HN: Open-Source App to Run 100× More AI Tools and Block Malicious Servers(github.com)

   1 points by algis-hn 1y ago|0 comments