Skip to content

AAK-MCP-OPENAPI-TANGLED-METHODS-001: OpenAPI path serving more than 4 HTTP methods or method-name/path semantic contradiction (Hermes TANGLED)

Severity
MEDIUM
Category
Tool Poisoning (tool-poisoning)
Scanner
agent_audit_kit/scanners/openapi_smells.py
Auto-fixable
No.
SARIF name
OpenApiTangledMethodsAndPaths

What it detects

An OpenAPI 3.x path operates as >4 HTTP methods (e.g. GET + POST + PUT + PATCH + DELETE all on the same path), OR the HTTP method contradicts the path segment (e.g. POST /get/... or GET /create/...). Per Hermes (arXiv:2605.14312), tangled path-and-method semantics confuse agents that infer operation intent from the path string. Side-effect-misclassification is the realized failure mode.

How to fix

Split the tangled path into >=2 disjoint paths, each owning <=4 methods with method-name and path-segment in semantic agreement. Reserve verbs (/get/..., /create/...) for their corresponding HTTP methods only.

To confirm the finding is gone, report only this rule:

agent-audit-kit scan . --rules AAK-MCP-OPENAPI-TANGLED-METHODS-001

Limitations

Compares only whole path segments with a verb list (get, list, fetch, read, create, add, new, update, edit, delete, remove): GET /users/create is reported, but GET /createUser and POST /users/get-by-email are not. More than four methods on one path is the other test. A spec over 1 MB is not read.

References


All rules. This page is generated from the rule registry when the documentation is built; to change it, change the rule in agent_audit_kit/rules/builtin.py. To give the rule a hand-written write-up, add docs/rules/AAK-MCP-OPENAPI-TANGLED-METHODS-001.md: the page then shows that text, with the registry reference appended under it.