Review the update before it changes your agents’ permissions.
A previously approved MCP or skill release adds a tool, broadens network access or changes its instructions.
All use casesMake the boundary explicit.
Retain the active pinned revision while the new artifact becomes a candidate. Compare source, requested permissions and tool definitions; test it in a bounded environment and review before activation.
Existing work continues on the approved release. New access is not silently distributed across every client. A tool description cannot approve itself.
Inspect the decision.
Continue using the approved pinned release.
Ready to evaluate
No external action
Select a variation and inspect the local example. This demonstration does not call a model or connect to a business system.
A signature proves provenance, not that all behavior is harmless. Evaluate actual permissions and behavior.
The controls behind the workflow.
Explore the capabilities that compose around this task, rather than treating each step as a separate product.
Related ways to use DriftGate.
A working environment should travel. Credentials should not.
A developer joins a payments project while also working on a public marketing website. The projects need different tools, instructions, accounts and restrictions.
Read-only should be a permission. Not a request.
A coding assistant investigates a production problem but attempts a destructive database operation during diagnosis.