AI agents call search_kev to retrieve information from Security Framework without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Based on sibling tools (search, compliance_map, cross_reference, get_* functions) which are all Read operations on security framework data, and the 'search_' prefix indicating query/retrieval without modification, this tool most likely retrieves vulnerability data from a database.
From the tool's definition Tool name 'search_kev' suggests searching/querying (KEV likely refers to CISA's Known Exploited Vulnerabilities catalog). No description provided, but naming pattern and server context indicate a retrieval operation.
Documented attack patterns abuse exactly the kind of access search_kev gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Security Framework, and nothing reaches the server without passing your rules. This is the rule we recommend for search_kev:
{
"version": "1",
"default": "deny",
"tools": {
"search_kev": {}
}
}search_kev 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.
search_kev. It is categorised as a Read tool in the Security Framework MCP Server, which means it retrieves data without modifying state.
Register the Security Framework MCP server in PolicyLayer and add a rule for search_kev: 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 Security Framework. Nothing to install.
search_kev 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 search_kev 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 search_kev. 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.
search_kev is provided by the Security Framework MCP server (zer0-kr/security-framework-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Security Framework, 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.
41 Security Framework tools catalogued and risk-classified — across an index of 43,000+ MCP servers.