Execute read-only GraphQL query.
AI agents call gitlab_execute_graphql_query to retrieve information from Gitlab without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool is explicitly described as 'read-only', meaning it only retrieves data without side effects. However, 'GraphQL' could theoretically include mutations, and the word 'execute' implies running arbitrary queries.
From the tool's definition Execute read-only GraphQL query
Documented attack patterns abuse exactly the kind of access gitlab_execute_graphql_query 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_execute_graphql_query:
{
"version": "1",
"default": "deny",
"tools": {
"gitlab_execute_graphql_query": {}
}
}gitlab_execute_graphql_query is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Execute read-only GraphQL query. It is categorised as a Read tool in the Gitlab MCP Server, which means it retrieves data without modifying state.
Register the Gitlab MCP server in PolicyLayer and add a rule for gitlab_execute_graphql_query: 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_execute_graphql_query 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 gitlab_execute_graphql_query 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_execute_graphql_query. 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_execute_graphql_query 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.