Save one file from a job artifacts archive to a local directory.
AI agents use gitlab_get_job_artifact_file_local to create or update resources in Gitlab — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Gitlab environment.
The tool writes/saves a file to the local filesystem, which is a write operation. It retrieves artifact data from GitLab (read) but the primary effect is persisting a file locally (write). Misuse could overwrite local files, but it's reversible. Severity is medium due to potential path traversal or overwrite risks on the local system.
From the tool's definition Save one file from a job artifacts archive to a local directory
Documented attack patterns abuse exactly the kind of access gitlab_get_job_artifact_file_local gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Gitlab, and nothing reaches the server without passing your rules. This is the rule we recommend for gitlab_get_job_artifact_file_local:
{
"version": "1",
"default": "deny",
"tools": {
"gitlab_get_job_artifact_file_local": {
"limits": [
{
"counter": "gitlab_get_job_artifact_file_local_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}gitlab_get_job_artifact_file_local stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Save one file from a job artifacts archive to a local directory. It is categorised as a Write tool in the Gitlab MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Gitlab MCP server in PolicyLayer and add a rule for gitlab_get_job_artifact_file_local: 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. Nothing to install.
gitlab_get_job_artifact_file_local is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the gitlab_get_job_artifact_file_local 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 gitlab_get_job_artifact_file_local. 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.
gitlab_get_job_artifact_file_local is provided by the Gitlab MCP server (mcpland/gitlab-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Gitlab, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
190 Gitlab tools catalogued and risk-classified — across an index of 43,000+ MCP servers.