What happened
The MCP permission model has a distinct allowSchemaChange flag that ExecuteCommandTool respects, but the two upsert tools do not. A UPSERT creating a new type slips past the flag, letting an agent exceed the schema-change boundary the operator configured.
Why it matters
An agent explicitly denied schema change can create types through upsert tools, breaking an operator's intended MCP permission boundary and leaving the schema modified.
Attack vector
The two MCP upsert tools build a Cypher MERGE and run it without gating on the MCP allowSchemaChange flag. A MERGE that names a type which does not exist analyzes as {CREATE, UPDATE} rather than a schema change, so a caller holding insert/update but explicitly denied schema change can create arbitrary new types.
Affected systems
ArcadeDB 26.3.1 before 26.11.1 (MCP upsert_entity / upsert_relationship tools)
Mitigation
Upgrade to ArcadeDB 26.11.1; advisory GHSA-6jr9-6vw5-xjf6 (also tracked with GHSA-r946-225c-5x88 / CVE group).