get_techniques_used_by_group_software
AI agents call get_techniques_used_by_group_software to retrieve information from MITRE ATT&CK MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries the MITRE ATT&CK knowledge base to retrieve information about techniques associated with threat groups and software. It performs no mutations, deletions, code execution, or financial operations. The naming convention ('get_*') and context among sibling read-only tools confirm it is a data retrieval function with no side effects.
From the tool's definition Tool name 'get_techniques_used_by_group_software' indicates a retrieval operation following the pattern of sibling tools like 'get_all_groups', 'get_all_software', and 'get_all_techniques' which are informational queries.
Documented attack patterns abuse exactly the kind of access get_techniques_used_by_group_software gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MITRE ATT&CK MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_techniques_used_by_group_software:
{
"version": "1",
"default": "deny",
"tools": {
"get_techniques_used_by_group_software": {}
}
} get_techniques_used_by_group_software 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_techniques_used_by_group_software. It is categorised as a Read tool in the MITRE ATT&CK MCP Server MCP Server, which means it retrieves data without modifying state.
Register the MITRE ATT&CK MCP Server MCP server in PolicyLayer and add a rule for get_techniques_used_by_group_software: 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 MITRE ATT&CK MCP Server. Nothing to install.
get_techniques_used_by_group_software 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_techniques_used_by_group_software 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_techniques_used_by_group_software. 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_techniques_used_by_group_software is provided by the MITRE ATT&CK MCP Server MCP server (stoyky/mitre-attack-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 55 MITRE ATT&CK MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
55 MITRE ATT&CK MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.