vulnerability_search

Search vulnerabilities/CVEs. RSQL q filter, e.g. q=vulnerabilitySensitivityLevel.sensitivityLevelName==

Server Vicarius vRx MCP Server space-c0wboy/vicarius-vrx-mcp-server
Category Read
Risk class Low
Parameters 00 required

What vulnerability_search does on Vicarius vRx MCP Server

AI agents call vulnerability_search to retrieve information from Vicarius vRx MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why vulnerability_search needs a policy

This tool retrieves vulnerability and CVE data using search filters with no capability to modify, delete, or execute operations. It is a pure data retrieval operation with no side effects, fitting the Read category. Severity is low because searching public vulnerability data poses minimal risk even if misused.

From the tool's definition Tool name includes 'search' and description explicitly states 'Search vulnerabilities/CVEs' with filter parameters. The RSQL query syntax (q=...) indicates a read-only query operation. Server description emphasizes 'read-only safety enforcement.'

Questions about vulnerability_search

What does the vulnerability_search tool do? +

Search vulnerabilities/CVEs. RSQL q filter, e.g. q=vulnerabilitySensitivityLevel.sensitivityLevelName==. It is categorised as a Read tool in the Vicarius vRx MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on vulnerability_search? +

Register the Vicarius vRx MCP Server MCP server in PolicyLayer and add a rule for vulnerability_search: 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 Vicarius vRx MCP Server. Nothing to install.

What risk level is vulnerability_search? +

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

Can I rate-limit vulnerability_search? +

Yes. Add a rate_limit block to the vulnerability_search 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 vulnerability_search completely? +

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

vulnerability_search is provided by the Vicarius vRx MCP Server MCP server (space-c0wboy/vicarius-vrx-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.