Search and get relevant context for any programming task. Exa-code has the highest quality and freshest context for libraries, SDKs, and APIs. Use this tool for ANY question or task for related to programming. RULE: when the user
AI agents call get_code_context_exa to retrieve information from Exa MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a Read operation: it retrieves and queries programming documentation and code examples from GitHub and related sources with no side effects. However, severity is medium rather than low because: (1) search tools can be used to enumerate sensitive information (private repos if accessible, API keys in code), (2) returned code context could inadvertently expose security practices or vulnerabilities, and (3)…
From the tool's definition Tool description states 'Search and get relevant context' and 'get relevant context for any programming task' — explicitly a retrieval/query operation. No modification, deletion, or code execution described.
Attacks that exploit this kind of access
Search and get relevant context for any programming task. Exa-code has the highest quality and freshest context for libraries, SDKs, and APIs. Use this tool for ANY question or task for related to programming. RULE: when the user. It is categorised as a Read tool in the Exa MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Exa MCP Server MCP server in PolicyLayer and add a rule for get_code_context_exa: 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 Exa MCP Server. Nothing to install.
get_code_context_exa 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_code_context_exa 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_code_context_exa. 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_code_context_exa is provided by the Exa MCP Server MCP server (jordyvandomselaar/exa-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 →