bitbucket-automation

The manifest/documentation is a functional and plausible Bitbucket automation skill. It does not contain embedded malware or hard-coded secrets. The principal supply-chain/security risk is architectural: all OAuth credentials and API payloads are brokered through a third-party MCP (https://rube.app/mcp) with no transparency about operator, token handling, retention, or logging. This creates a high-impact trust boundary where exfiltration or unauthorized actions are possible if the MCP is malicious or compromised. Recommended mitigations before adoption: verify MCP operator identity and audit results, insist on minimal OAuth scopes and short-lived tokens, require explicit multi-step confirmation (and re-authentication) for destructive actions, log and monitor actions locally, and prefer direct API calls or a self-hosted trusted proxy when handling sensitive repos.