使用 MCP 客户端创建的测试仓库
AI agents use create_gitlab_repository to create or update resources in GitLab MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your GitLab MCP Server environment.
Creating a GitLab repository is a reversible modification operation—repositories can be deleted afterward. This falls under Write category rather than Execute because the tool's primary effect is data creation, not arbitrary code execution.
From the tool's definition Tool name 'create_gitlab_repository' and server description states it supports 'creating projects' and 'repository and branch management'. The description confirms creation of repositories, which is a write operation.
Attacks that exploit this kind of access
使用 MCP 客户端创建的测试仓库. It is categorised as a Write tool in the GitLab MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the GitLab MCP Server MCP server in PolicyLayer and add a rule for create_gitlab_repository: 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.
create_gitlab_repository 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 create_gitlab_repository 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 create_gitlab_repository. 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.
create_gitlab_repository is provided by the GitLab MCP Server MCP server (masx200/gitlab-mcp-server). 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 →