Troubleshooting

Use this page when team adoption stalls because the policy is too vague, too strict, or poorly scoped.

Policy Objective

Give teams a way to fix governance friction without dropping security or accuracy.

Common Problems

  • no one owns the approved tool list
  • prompts are shared in chat instead of versioned in repo
  • MCP pilots expand before approval catches up
  • teams confuse Documentation verified with Locally tested
  • assign an owner
  • publish the current approval state
  • move prompts and templates into version control
  • tighten validation and review checkpoints

Escalation Triggers

  • repeated unsafe prompts
  • unexplained permission widening
  • tool sprawl across teams
  • unclear incident response after a bad automation action

Copy-Ready Troubleshooting Template

Problem:
Owner:
Affected team:
Current risk:
Immediate containment:
Longer-term policy fix:
Review date:

Verification Note

Operational guidance only. Each organization should map this to its own incident and change-management process.

Sources