MCP governance
Inventory, per-server and per-tool rules, routed endpoints, rug-pull tripwire, lethal trifecta.
Overview
MCP governance MCP servers give AI agents tools — file access, browsers, deploy keys. Sentilai go...
Per-server rules
MCP Inventory lists every MCP server Sentilai has seen — discovered on developer machines by the ...
Per-tool rules
A per-server rule is sometimes too blunt: you want github available, but not delete_repository. ...
Routed endpoints
Most MCP servers run locally on the developer's machine, and the Endpoint Suite wraps them automa...
What MCP is and why it needs governing
Model Context Protocol is how an AI assistant gets hands. Without it, an assistant can only produ...
Approve and review new servers
The workflow that turns MCP from a free-for-all into something you have decided about. Turning it...
MCP protocol versions
The Protocol column on MCP Inventory shows which version of the Model Context Protocol each serve...
When a tool changes underneath you
You reviewed a server, approved it, and moved on. Three weeks later its send_email tool quietly ...
Tool-result injection
Prompt injection does not only arrive in prompts. The most effective route into an agent is throu...
Hallucinated and vulnerable packages
A distinctive failure mode of AI coding assistants: they confidently suggest installing packages ...