Get object by STIX ID (case-sensitive)
AI agents call get_object_by_stix_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.
This tool retrieves threat intelligence data from the MITRE ATT&CK knowledge base by a specific identifier. It performs a lookup operation without creating, modifying, deleting, or executing anything. The blast radius of misuse is minimal—an agent could only access existing threat intelligence data, which is already public. This is a standard read/query pattern typical of knowledge base access tools.
From the tool's definition Tool name 'get_object_by_stix_id' and description 'Get object by STIX ID' indicate a retrieval/query operation. The verb 'Get' and the context of querying a knowledge base (MITRE ATT&CK) confirm this is a read-only operation with no side effects.
Documented attack patterns abuse exactly the kind of access get_object_by_stix_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_stix_id:
{
"version": "1",
"default": "deny",
"tools": {
"get_object_by_stix_id": {}
}
}get_object_by_stix_id 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 object by STIX ID (case-sensitive). 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_object_by_stix_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.
get_object_by_stix_id 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_object_by_stix_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.
Set action: deny in the PolicyLayer policy for get_object_by_stix_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.
get_object_by_stix_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.
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.