perso — a WebAssembly policy engine that decides what your MCP agent is allowed to do

If you’re building anything on top of MCP (Model Context Protocol), you’ll eventually hit this question: once an LLM decides to call a tool, who actually checks whether it’s allowed to? MCP’s spec defines how tools are discovered and invoked — it says nothing about who’s allowed to call what, or und…

View Post on Scour ↗

More from DEV Community on Scour.