convex_analyze_http
Analyze convex/http.ts for HTTP endpoint issues: duplicate routes, missing CORS headers, missing OPTIONS preflight handlers, missing httpRouter/httpAction imports, and missing default export. Returns route inventory with methods and paths.
This record as markdown: /tools/io-github-homenshum-nodebench/convex-analyze-http.md
What convex_analyze_http does on Nodebench
AI agents call convex_analyze_http to retrieve information from Nodebench without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why convex_analyze_http is rated Low
This tool reads and analyzes source code to detect configuration issues (duplicate routes, missing headers, missing handlers). It performs no side effects—no code execution, no data modification, no external API calls. While the findings could inform risky changes, the tool itself is purely informational.
From the tool's definition Tool performs static analysis of TypeScript files ('Analyze convex/http.ts') to identify HTTP endpoint issues and returns 'route inventory' without modifying code or executing requests.
Attacks that exploit this kind of access
The rule that runs convex_analyze_http safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Nodebench, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For convex_analyze_http, this is the rule to start with:
convex_analyze_http is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Nodebench, apply this rule, and every convex_analyze_http call is checked against it from then on.
Questions about convex_analyze_http
Analyze convex/http.ts for HTTP endpoint issues: duplicate routes, missing CORS headers, missing OPTIONS preflight handlers, missing httpRouter/httpAction imports, and missing default export. Returns route inventory with methods and paths. It is categorised as a Read tool in the Nodebench MCP Server, which means it retrieves data without modifying state.
Register the Nodebench MCP server in PolicyLayer and add a rule for convex_analyze_http: 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 Nodebench. Nothing to install.
convex_analyze_http 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 convex_analyze_http 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 convex_analyze_http. 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.
convex_analyze_http is provided by the Nodebench MCP server (nodebench-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Nodebench, and thousands of servers like it.
This server
Across the catalogue