get_pipeline_step_log
AI agents call get_pipeline_step_log to retrieve information from MCP Atlassian + Bitbucket without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool appears to retrieve log data from a pipeline step, which is a non-destructive query operation. Even though logs may contain sensitive information (which would increase severity if leaked), the tool itself performs only retrieval. The empty description reduces confidence slightly, but the naming pattern and server context strongly suggest a Read operation.
From the tool's definition Tool name 'get_pipeline_step_log' indicates retrieval of pipeline execution logs. No description provided, but the 'get_' prefix and context of sibling tools (download_attachment, get_agile_boards, get_all_projects) suggest a read-only operation that…
Attacks that exploit this kind of access
get_pipeline_step_log. It is categorised as a Read tool in the MCP Atlassian + Bitbucket MCP Server, which means it retrieves data without modifying state.
Register the MCP Atlassian + Bitbucket MCP server in PolicyLayer and add a rule for get_pipeline_step_log: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches MCP Atlassian + Bitbucket. Nothing to install.
get_pipeline_step_log is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_pipeline_step_log rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for get_pipeline_step_log. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
get_pipeline_step_log is provided by the MCP Atlassian + Bitbucket MCP server (jellythomas/mcp-atlassian-with-bitbucket). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →