AI agents call vuln_match to retrieve information from ThreatMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and aggregates vulnerability intelligence data for vendor products. It is a read/query operation that fetches existing threat intelligence with no side effects, modifications, or destructive actions.
From the tool's definition 产品漏洞匹配：通过厂商产品匹配功能，聚合相关厂商产品的漏洞信息 (Product vulnerability matching: aggregates vulnerability information for relevant vendor products through vendor product matching)
Documented attack patterns abuse exactly the kind of access vuln_match gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and ThreatMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for vuln_match:
{
"version": "1",
"default": "deny",
"tools": {
"vuln_match": {}
}
}vuln_match is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
产品漏洞匹配：通过厂商产品匹配功能，聚合相关厂商产品的漏洞信息. It is categorised as a Read tool in the ThreatMCP MCP Server, which means it retrieves data without modifying state.
Register the Threat MCP server in PolicyLayer and add a rule for vuln_match: 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 ThreatMCP. Nothing to install.
vuln_match 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 vuln_match 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 vuln_match. 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.
vuln_match is provided by the Threat MCP server (naxg/threatmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from ThreatMCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
15 ThreatMCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.