Low Risk

get_object_by_attack_id

get_object_by_attack_id

How to control get_object_by_attack_id ↓

AI agents call get_object_by_attack_id 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 an object from the MITRE ATT&CK database by its ID. It performs no modifications, deletions, or external operations. The 'get_' prefix and consistency with other data retrieval tools on this server confirm it is a read-only query operation.

From the tool's definition Tool name 'get_object_by_attack_id' indicates a retrieval operation using an identifier. The pattern matches other sibling tools on this server (get_all_assets, get_all_campaigns, get_all_groups, etc.) which are clearly read-only query functions against the…

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

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

get_object_by_attack_id 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_object_by_attack_id tool do? +

get_object_by_attack_id. 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_object_by_attack_id? +

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

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

Can I rate-limit get_object_by_attack_id? +

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

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

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