New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

cve_lookup

Search NIST NVD CVE API 2.0 by product/keyword with optional CVSSv3 severity filter. Returns CVE ids, scores, vectors, descriptions and reference URLs. Public NVD data. Price: $0.01 USDC per successful call (x402, Solana). Same tool over HTTPS: GET https://scorptech.it.com/api/x402/v1/cve-lookup

SERVERScorpTech x402 API SOURCEhttps://scorptech.it.com/api/x402/mcp
Low RISK CLASS
Category Read
Parameters 21 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-it-scorptech-x402/cve-lookup.md

What cve_lookup does on ScorpTech x402 API

AI agents call cve_lookup to retrieve information from ScorpTech x402 API without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

ParameterTypeRequiredDescription
product string Yes Product or keyword
severity string — Optional LOW|MEDIUM|HIGH|CRITICAL

Parameters from the server's own tool schema.

Why cve_lookup is rated Low

Even though cve_lookup only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Questions about cve_lookup

What does the cve_lookup tool do? +

Search NIST NVD CVE API 2.0 by product/keyword with optional CVSSv3 severity filter. Returns CVE ids, scores, vectors, descriptions and reference URLs. Public NVD data. Price: $0.01 USDC per successful call (x402, Solana). Same tool over HTTPS: GET https://scorptech.it.com/api/x402/v1/cve-lookup. It is categorised as a Read tool in the ScorpTech x402 API MCP Server, which means it retrieves data without modifying state.

What parameters does cve_lookup accept? +

cve_lookup accepts 2 parameters: product, severity. Required: product. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on cve_lookup? +

Register the ScorpTech x402 API MCP server in PolicyLayer and add a rule for cve_lookup: 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 ScorpTech x402 API. Nothing to install.

What risk level is cve_lookup? +

cve_lookup is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit cve_lookup? +

Yes. Add a rate_limit block to the cve_lookup 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.

How do I block cve_lookup completely? +

Set action: deny in the PolicyLayer policy for cve_lookup. 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.

What MCP server provides cve_lookup? +

cve_lookup is provided by the ScorpTech x402 API MCP server (https://scorptech.it.com/api/x402/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on ScorpTech x402 API, and thousands of servers like it.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of ScorpTech x402 API's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.