取得 Job 的執行日誌
AI agents call get_job_log to retrieve information from GitLab MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns existing log data from a CI/CD job without creating, modifying, deleting, or executing any operations. It is purely informational retrieval, making it a Read category tool with low severity risk.
From the tool's definition get_job_log retrieves Job execution logs (取得 Job 的執行日誌 means 'retrieve Job execution log'). The verb 'get' and action of retrieving logs indicate read-only access with no side effects or modifications.
Attacks that exploit this kind of access
取得 Job 的執行日誌. It is categorised as a Read tool in the GitLab MCP Server MCP Server, which means it retrieves data without modifying state.
Register the GitLab MCP Server 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 GitLab MCP Server. 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 GitLab MCP Server MCP server (snowild/gitlab-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
get_job_log is one line of GitLab MCP Server's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →