AI agents call get_attack_pattern 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 appears to retrieve attack pattern data from the security framework knowledge base, similar to other 'get_*' utilities on the server. No indication of modification, deletion, code execution, or financial impact. Classified as Read with lowered confidence (0.75) due to empty description, but the naming pattern and server context provide reasonable evidence.
From the tool's definition Tool name 'get_attack_pattern' indicates data retrieval operation. The description is empty, but sibling tools on this security-framework server (get_api_top10, get_asvs, get_cve_detail, get_cheatsheet) are all read-only information retrieval functions.
Documented attack patterns abuse exactly the kind of access get_attack_pattern 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_attack_pattern:
{
"version": "1",
"default": "deny",
"tools": {
"get_attack_pattern": {}
}
}get_attack_pattern 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.
get_attack_pattern. 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_attack_pattern: 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_attack_pattern 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_pattern 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_pattern. 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_pattern 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.