Get CPGQL syntax documentation and common query patterns.
AI agents call get_cpgql_syntax_help to retrieve information from CodeBadger without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool provides documentation and reference material for CPGQL syntax. It retrieves and presents static information about query language patterns without executing those queries against any codebase, modifying data, or triggering external operations. The read-only nature and absence of any side-effect capability makes this a straightforward Read classification with low severity.
From the tool's definition Tool description states it 'Get[s] CPGQL syntax documentation and common query patterns' — purely informational retrieval with no capability to execute queries, modify code, or trigger side effects.
Attacks that exploit this kind of access
Get CPGQL syntax documentation and common query patterns. It is categorised as a Read tool in the CodeBadger MCP Server, which means it retrieves data without modifying state.
Register the CodeBadger MCP server in PolicyLayer and add a rule for get_cpgql_syntax_help: 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 CodeBadger. Nothing to install.
get_cpgql_syntax_help 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_cpgql_syntax_help 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_cpgql_syntax_help. 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_cpgql_syntax_help is provided by the CodeBadger MCP server (lekssays/codebadger). 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 →