AML.T0085.001
AI Agent Tools

MITRE source definition

Adversaries may prompt the AI service to invoke various tools the agent has access to. Tools may retrieve data from different APIs or services in an organization.

Source modified 2026-05-27. Reproduced from the pinned ATLAS release; inline technique links resolve to local reference pages.

Parent, sub-techniques and ATT&CK references

• AML.T0085 Data from AI Services — parent

Source-backed defensive context

MITRE mitigations

• AML.M0024 AI Telemetry Logging
• AML.M0026 Privileged AI Agent Permissions Configuration
• AML.M0027 Single-User AI Agent Permissions Configuration
• AML.M0028 AI Agent Tools Permissions Configuration
• AML.M0032 Segmentation of AI Agent Components

MITRE case studies

• AML.CS0037 Data Exfiltration via Agent Tools in Copilot Studio · Exercise
• AML.CS0038 Planting Instructions for Delayed Automatic AI Agent Tool Invocation · Exercise
• AML.CS0039 Living Off AI: Prompt Injection via Jira Service Management · Exercise
• AML.CS0063 Prompt-Based Attacks Against Gemini via Calendar Invitations · Exercise
• AML.CS0066 ZombieAgent: Data Exfiltration Attack on ChatGPT · Exercise

These are explicit source relationships, not independently reproduced incidents or validated detection coverage.

Simulation and telemetry boundary

This is a technique reference page, not a runnable simulation. No ATLAS-specific telemetry mapping, local attack execution or detector validation is asserted. MITRE maturity describes its source evidence, not a 1200km lab result.

For broader context—not technique-specific control mappings—see AI Security, AI Security Course, and detection-validation methodology.

Provenance and attribution

Immutable MITRE ATLAS source · Import provenance · Attribution and transformation notice · Apache License 2.0

Copyright 2021-2026 MITRE. Source text and explicit relationships are retained; navigation, formatting and local links are provided by 1200km.

No explicit relationship in this pinned source.