Appearance
Why It Matters
Duplicate tool names create ambiguity in machine-consumed tool catalogs. One tool can shadow another, or clients can behave inconsistently about which definition wins.
What Triggers
SEC315 applies to MCP-style tool descriptor collections and triggers when the same tool name appears more than once in the parsed collection.
Example that triggers:
json
[
{ "name": "list_clusters", "inputSchema": { "type": "object", "properties": {}, "additionalProperties": false } },
{ "name": "list_clusters", "inputSchema": { "type": "object", "properties": {}, "additionalProperties": false } }
]False Positives
This is a deterministic structural check over parsed tool names. If duplicate names are intentional, the safer fix is still to make the identifiers unique and keep aliases in descriptive fields instead.
Remediation
Rename the duplicated tool so each exported machine identifier is unique.