Low Risk

get_campaigns_by_alias

Get campaigns by their alias

How to control get_campaigns_by_alias ↓

AI agents call get_campaigns_by_alias 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 campaign information from the MITRE ATT&CK knowledge base using an alias parameter. It performs a read-only lookup operation with no side effects—it does not create, modify, delete, execute code, or affect external systems. The action is purely informational retrieval, consistent with other Read category tools like 'get_all_campaigns' on the same server.

From the tool's definition Tool name 'get_campaigns_by_alias' and description 'Get campaigns by their alias' indicate a query/retrieval operation with no modification capability.

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

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

get_campaigns_by_alias 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_campaigns_by_alias tool do? +

Get campaigns by their alias. 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_campaigns_by_alias? +

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

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

Can I rate-limit get_campaigns_by_alias? +

Yes. Add a rate_limit block to the get_campaigns_by_alias 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_campaigns_by_alias completely? +

Set action: deny in the PolicyLayer policy for get_campaigns_by_alias. 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_campaigns_by_alias? +

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