Low Risk

get_techniques_used_by_campaign

Get techniques used by campaign

How to control get_techniques_used_by_campaign ↓

AI agents call get_techniques_used_by_campaign 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.

Low Risk

This tool retrieves and queries data from the MITRE ATT&CK knowledge base without modifying, deleting, or executing any operations. It is informational in nature, supporting threat analysis and research. No reversible modifications, code execution, financial transactions, or destructive actions are involved.

From the tool's definition Tool name 'get_techniques_used_by_campaign' and description 'Get techniques used by campaign' indicate a retrieval operation that queries the MITRE ATT&CK knowledge base for techniques associated with a campaign.

Documented attack patterns abuse exactly the kind of access get_techniques_used_by_campaign 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_campaign:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_techniques_used_by_campaign": {}
  }
}

get_techniques_used_by_campaign is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register MITRE ATT&CK MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the get_techniques_used_by_campaign tool do? +

Get techniques used by campaign. It is categorised as a Read tool in the MITRE ATT&CK MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_techniques_used_by_campaign? +

Register the MITRE ATT&CK MCP Server MCP server in PolicyLayer and add a rule for get_techniques_used_by_campaign: 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.

What risk level is get_techniques_used_by_campaign? +

get_techniques_used_by_campaign is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_techniques_used_by_campaign? +

Yes. Add a rate_limit block to the get_techniques_used_by_campaign 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.

How do I block get_techniques_used_by_campaign completely? +

Set action: deny in the PolicyLayer policy for get_techniques_used_by_campaign. 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.

What MCP server provides get_techniques_used_by_campaign? +

get_techniques_used_by_campaign 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.

Enforce policy on every MITRE ATT&CK MCP Server tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.