Get the log output of a CI job (last 2000 chars).
AI agents call get_job_log 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 only retrieves and displays existing CI job log data. It does not create, modify, delete, execute commands, or affect financial systems. Reading CI logs is a standard diagnostic operation with minimal security risk—the blast radius is limited to information disclosure of what may already be visible to authorized users. Confidence is high because the description is clear and unambiguous.
From the tool's definition Tool retrieves log output of a CI job (a read/retrieval operation with no modification) as stated in the description 'Get the log output of a CI job (last 2000 chars).' No side effects or data changes occur.
Attacks that exploit this kind of access
Get the log output of a CI job (last 2000 chars). 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: 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 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 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. 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 is provided by the Mcp Gitlab MCP server (wanadev/gitlab-mcp). 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 →