Get the log (trace) output of a CI/CD job.
AI agents call get_job_log_tool to retrieve information from MCP Gitlab without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries existing job log data from GitLab's CI/CD system. It performs no writes, deletions, code execution, or financial transactions. The worst-case misuse would be unauthorized access to CI/CD logs, which is a read-based confidentiality risk rather than an integrity or availability risk.
From the tool's definition Tool name 'get_job_log_tool' and description 'Get the log (trace) output of a CI/CD job' indicate a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
Get the log (trace) output of a CI/CD job. It is categorised as a Read tool in the MCP Gitlab MCP Server, which means it retrieves data without modifying state.
Register the MCP Gitlab MCP server in PolicyLayer and add a rule for get_job_log_tool: 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 Gitlab. Nothing to install.
get_job_log_tool 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_job_log_tool 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_job_log_tool. 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_job_log_tool is provided by the MCP Gitlab MCP server (mcp-gitlab-crunchtools). 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 →