Bug: When jira-write is disabled but Jira Integration is added, agent will bypass the MCP to perform a write using Jira API

[squizzi]

🐛 Bug Description

Summary: If jira-write is disabled the agent will often bypass the MCP and just make the write itself using an alternate method like an API endpoint.

Expected Behavior: That should probably be prevented when jira-write is set to off and the agent should not attempt write behavior.

Actual Behavior: It'll try to call the Jira MCP, see that add-comment or whatever writeable Jira tool is unavailable and then use curl to perform a write.

🔄 Steps to Reproduce

1. Add a Jira integration
2. Keep the jira-write feature flag off
3. Prompt a session to perform a comment add or some other form of writeable Jira MCP interaction and watch it sometimes try to do it anyway.

🖼️ Screenshots

If applicable, add screenshots to help explain your problem.

🌍 Environment

Component: [RAT System / Ambient Agentic Runner / vTeam Tools]
Ambient Runner

Version/Commit: [e.g. v1.2.3 or commit hash]
v0.2.14

🔍 Possible Solution

Perhaps we could add some prompt context to the runner when jira-write is disabled and Jira integration is enabled to disallow using alternatives outside of the MCP but I feel that'll have unintended effects AND perhaps the agent might just ignore that entirely.

✅ Acceptance Criteria

• Bug is reproduced and root cause identified
• Fix is implemented and tested
• Regression tests added to prevent future occurrences
• Documentation updated if needed
• Fix is verified in staging environment

🏷️ Labels

• Priority: [low/medium/high/critical]
• Complexity: [trivial/easy/medium/hard]
• Component: [frontend/backend/operator/tools/docs]