Map a CVE to MITRE ATT&CK techniques and associated threat groups. Downloads the ATT&CK dataset lazily (cached 24h). Searches technique descriptions and references for the CVE ID. Args: cve_id: CVE identifier (e.g. CVE-2021-44228)
AI agents call get_attack_mapping to retrieve information from CVE MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a read-only query operation that correlates vulnerability identifiers with threat intelligence datasets. It downloads and searches cached threat intelligence data to return mapping results, with no side effects, data modification, or code execution.
From the tool's definition Tool description explicitly states it 'Map[s] a CVE to MITRE ATT&CK techniques' and 'Searches technique descriptions and references' — operations that retrieve and query existing data from the ATT&CK dataset without modification, deletion, or execution of…
Documented attack patterns abuse exactly the kind of access get_attack_mapping gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and CVE MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_attack_mapping:
{
"version": "1",
"default": "deny",
"tools": {
"get_attack_mapping": {}
}
}get_attack_mapping 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.
Map a CVE to MITRE ATT&CK techniques and associated threat groups. Downloads the ATT&CK dataset lazily (cached 24h). Searches technique descriptions and references for the CVE ID. Args: cve_id: CVE identifier (e.g. CVE-2021-44228). It is categorised as a Read tool in the CVE MCP Server MCP Server, which means it retrieves data without modifying state.
Register the CVE MCP Server MCP server in PolicyLayer and add a rule for get_attack_mapping: 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 CVE MCP Server. Nothing to install.
get_attack_mapping 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 get_attack_mapping 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 get_attack_mapping. 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.
get_attack_mapping is provided by the CVE MCP Server MCP server (mukul975/cve-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from CVE MCP Server, 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.
27 CVE MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.