bitbucket_get_pipeline

What bitbucket_get_pipeline does on Sage MCP

AI agents call bitbucket_get_pipeline to retrieve information from Sage MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why bitbucket_get_pipeline is rated Low

This tool retrieves or queries data about a pipeline run (status, logs, results, etc.) with no side effects. It falls squarely under Read category. The severity is low because pipeline details are typically informational and would not cause significant harm if accessed by an AI agent, though in a multi-tenant environment with isolated servers, access control via OAuth/API key mitigates most concerns.

From the tool's definition Tool name 'bitbucket_get_pipeline' and description 'Get details of a specific pipeline run' indicate retrieval of pipeline execution information without modification or execution of operations.

The rule that runs bitbucket_get_pipeline safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Sage MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For bitbucket_get_pipeline, this is the rule to start with:

{
  "version": "1",
  "default": "deny",
  "tools": {
    "bitbucket_get_pipeline": {}
  }
}

Questions about bitbucket_get_pipeline