AI agents call codeql_summary to retrieve information from Musubix without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool reads and aggregates pre-existing security findings from SARIF (Static Analysis Results Interchange Format) data. It performs no mutations, code execution, or destructive operations—it only queries and presents analysis results. This is a classic Read operation with minimal risk: it cannot alter systems, trigger external operations, or cause side effects beyond returning information.
From the tool's definition The tool 'Get a summary of security findings from parsed SARIF data' retrieves and summarizes existing security analysis results. The verb 'Get' and 'summary' indicate data retrieval without modification or execution of code.
Attacks that exploit this kind of access
Get a summary of security findings from parsed SARIF data. It is categorised as a Read tool in the Musubix MCP Server, which means it retrieves data without modifying state.
Register the Musubix MCP server in PolicyLayer and add a rule for codeql_summary: 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 Musubix. Nothing to install.
codeql_summary 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 codeql_summary 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 codeql_summary. 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.
codeql_summary is provided by the Musubix MCP server (@nahisaho/musubix-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 →