Enhanced code search with relationship context and related components
AI agents call query_code_with_context to retrieve information from SACL MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs semantic code search and retrieval with contextual augmentation. It fetches and analyzes existing code relationships without modifying, executing, or deleting data. The word 'search' and 'query' in the name and description, combined with the context-retrieval nature of sibling tools, confirm Read category.
From the tool's definition Tool name 'query_code' with description 'Enhanced code search with relationship context and related components' indicates retrieval and querying operations.
Attacks that exploit this kind of access
Enhanced code search with relationship context and related components. It is categorised as a Read tool in the SACL MCP Server MCP Server, which means it retrieves data without modifying state.
Register the SACL MCP Server MCP server in PolicyLayer and add a rule for query_code_with_context: 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 SACL MCP Server. Nothing to install.
query_code_with_context 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 query_code_with_context 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 query_code_with_context. 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.
query_code_with_context is provided by the SACL MCP Server MCP server (ulasbilgen/sacl). 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 →