cve_export
AI agents use cve_export to create or update resources in CVE Risk MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your CVE Risk MCP Server environment.
An AI agent can call cve_export faster than any human can review — one bad instruction and it creates or modifies resources in CVE Risk MCP Server by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
cve_export. It is categorised as a Write tool in the CVE Risk MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the CVE Risk MCP Server MCP server in PolicyLayer and add a rule for cve_export: 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 Risk MCP Server. Nothing to install.
cve_export is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the cve_export 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 cve_export. 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.
cve_export is provided by the CVE Risk MCP Server MCP server (sarveshkapre/cve-risk-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the 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 →