AML.T0099 · AI Agent Tool Data Poisoning

Explore 1 source-supported AI security cases for AML.T0099 · AI Agent Tool Data Poisoning in MITRE ATLAS, with evidence, scope, and defensive analysis.

Risk category

Adversaries may manipulate data in a victim-controlled, trusted, or connected data source that is accessible through an AI agent tool. Poisoned data may be placed in document repositories, databases, source-code repositories, knowledge bases, search indexes, enterprise applications, or third-party data services used by the agent. The content may be crafted to appear in common tool queries or retrieval operations. It may contain false or misleading information or malicious instructions intended to produce an [LLM Prompt Injection: Indirect](/techniques/AML.T0051.001) when retrieved. This technique concerns manipulation of a data source that an agent tool treats as a source of information. When the adversary introduces the content through a victim-controlled public-facing application, the activity may also constitute [Prompt Infiltration via Public-Facing Application](/techniques/AML.T0093). Content retrieved directly from an adversary-controlled website may instead constitute [Drive-by Compromise](/techniques/AML.T0078). A malicious or compromised tool that deliberately alters its own runtime result constitutes [AI Agent Tool Poisoning: Runtime Response](/techniques/AML.T0110.002).

Official framework source ↗ · Open interactive explorer ↗

Validated Research ·

Agentjacking: How Fake Sentry Errors Turn MCP Telemetry into Agent Code Execution

Tenet Threat Labs showed that attacker-injected Sentry events (error-monitoring records from the Sentry observability platform) can hijack AI coding agents through the Sentry MCP server. A public Sentry DSN lets an attacker submit a crafted error, the MCP integration returns it as diagnostic context, and Claude Code, Cursor, or Codex may execute a suggested npm command with developer or CI privileges. The control lesson: telemetry is data, not authority; MCP outputs, agent clients, tool gates, sandboxes, and egress policy all need runtime enforcement.

ATLAS annotations follow the source SecureFlow steps; they are not a MITRE endorsement of cross-framework mappings.

AIA · Read the full case ↗ · SecureFlow · Read the full case ↗