AID-H-024: Tool & MCP Resolution Integrity

Version 1.20261015 · Family — navigation only

Enforce deterministic, verified resolution of tools and Model Context Protocol (MCP) endpoints to prevent typosquatting, alias collision, and registry-based misdirection. Resolution must be fail-closed: ambiguous matches require explicit disambiguation rather than best-guess selection. This ensures that when an agent calls a tool, it binds to the exact, authorized namespace, version, and descriptor bytes intended.

Scope boundary

Owns consuming-side resolution of the exact approved tool or MCP identity, namespace, version, descriptor bytes, and contract semantics, including fail-closed handling of ambiguity and drift.

AID-H-028.001: AID-H-024 resolves which logical tool or MCP endpoint is intended; AID-H-028.001 authenticates the selected server transport before connection. Correct logical resolution does not prove transport identity, and a valid connection does not prove that the intended tool contract was selected.

AID-H-034.004: AID-H-024 verifies server-published descriptors from the consumer side; AID-H-034.004 governs what an MCP server is allowed to publish. Publication approval and consuming-side resolution are independent enforcement points.

AID-H-018.002: AID-H-024 decides which approved tool contract a reference resolves to; AID-H-018.002 decides whether the authenticated principal may invoke it for the requested object and action. Resolution establishes identity, not runtime authorization.

Sub-techniques

Threat mappings

MITRE ATLAS

MAESTRO

OWASP LLM Top 10 2026

OWASP ML Top 10 2023

OWASP Top 10 for Agentic Applications 2026

NIST Adversarial Machine Learning 2025

Cisco Integrated AI Security and Safety Framework

Google Secure AI Framework 2.0 - Risks

Databricks AI Security Framework 3.0

AID-H-024: Tool & MCP Resolution Integrity | AIDEFEND

Loading interactive view…

A Practical Knowledge Base for AI Security Defenses

Version