MCP Server Policy
EXA MCP POLICY
Enforce policies on every tool call to the Exa MCP Server. 8 tools listed, categorised, and ready for rules.
GET STARTED
Download this policy scaffold and add your rules. Intercept enforces them on every tool call before it reaches Exa.
# Download policy scaffold
curl -o exa.yaml https://raw.githubusercontent.com/policylayer/intercept/main/policies/exa.yaml
# Run with Intercept
intercept --policy exa.yaml -- npx -y @exa-labs/exa-mcp-server Server documentation: https://github.com/exa-labs/exa-mcp-server
READ TOOLS
4OTHER TOOLS
4POLICY YAML
This scaffold lists every tool with empty rules. Add conditions — rate limits, argument validation, deny rules — then deploy with Intercept.
version: "1"
description: "Policy for exa-labs/exa-mcp-server"
default: "allow"
tools:
get_code_context_exa:
rules: []
people_search_exa:
rules: []
web_search_advanced_exa:
rules: []
web_search_exa:
rules: []
company_research_exa:
rules: []
crawling_exa:
rules: []
deep_researcher_check:
rules: []
deep_researcher_start:
rules: [] RELATED POLICIES
FREQUENTLY ASKED QUESTIONS
What tools does the Exa MCP server expose?
The Exa MCP Server exposes 8 tools across 2 categories: Read, Other. Each tool can be individually controlled with Intercept policies.
How do I enforce policies on Exa?
Download the policy scaffold, add rules (rate limits, argument validation, deny rules), then run Intercept as a proxy in front of the Exa MCP server. Every tool call is evaluated against your YAML policy before execution.
Is the Exa policy free to use?
Yes. All Intercept policies are open source under the Apache 2.0 licence. Download, modify, and deploy without restrictions.
ENFORCE POLICIES ON EXA
Open source. One binary. Zero dependencies.