Look up a CWE (Common Weakness Enumeration) by ID with description and OWASP cross-references.
AI agents call get_cwe 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.
The tool performs a simple lookup/query of static security reference data (CWE definitions and cross-references). It retrieves information without modifying, executing, deleting, or creating anything. This is a read-only data retrieval operation with minimal risk.
From the tool's definition Tool description states 'Look up a CWE...with description and OWASP cross-references' — a pure retrieval operation with no side effects.
Documented attack patterns abuse exactly the kind of access get_cwe 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 get_cwe:
{
"version": "1",
"default": "deny",
"tools": {
"get_cwe": {}
}
}get_cwe 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.
Look up a CWE (Common Weakness Enumeration) by ID with description and OWASP cross-references. 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 get_cwe: 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.
get_cwe 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_cwe 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_cwe. 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_cwe 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.