Repro
mxcli v0.18.0, Mendix 11.12.2 project, security level Production.
$ ./mxcli -p eShopMendix.mpr -c "SHOW ACCESS ON ENTITY eShop.CatalogBrand"
Parse error: line 1:60 extraneous input '.' expecting the start of a statement
(create, alter, drop, show, describe, …)
$ ./mxcli -p eShopMendix.mpr -c 'SHOW ACCESS ON ENTITY "eShop"."CatalogBrand"'
Parse error: line 1:55 extraneous input '"eShop"' expecting the start of a statement
$ ./mxcli -p eShopMendix.mpr -c "SHOW ACCESS ON PAGE eShop.Foo" # parses fine
$ ./mxcli -p eShopMendix.mpr -c "SHOW ACCESS ON MICROFLOW eShop.Foo" # parses fine
Quoting the identifiers does not help — it moves the error earlier, to the module name itself.
Expected
SHOW ACCESS ON ENTITY <module>.<entity> should report the entity's access rules, symmetric with
the PAGE and MICROFLOW variants that already work.
This exact form is documented in the CLAUDE.md that mxcli init generates:
SHOW ACCESS ON MICROFLOW|PAGE|ENTITY Mod.Name — Role access on element
So generated guidance tells an agent to run a statement the binary rejects.
Workaround
SHOW SECURITY MATRIX IN <module> gives equivalent evidence, so this is not blocking — but it
costs a failed command and a detour every time, and an agent following the generated CLAUDE.md
hits it before finding the alternative.
Repro
mxcli
v0.18.0, Mendix 11.12.2 project, security level Production.Quoting the identifiers does not help — it moves the error earlier, to the module name itself.
Expected
SHOW ACCESS ON ENTITY <module>.<entity>should report the entity's access rules, symmetric withthe PAGE and MICROFLOW variants that already work.
This exact form is documented in the
CLAUDE.mdthatmxcli initgenerates:So generated guidance tells an agent to run a statement the binary rejects.
Workaround
SHOW SECURITY MATRIX IN <module>gives equivalent evidence, so this is not blocking — but itcosts a failed command and a detour every time, and an agent following the generated CLAUDE.md
hits it before finding the alternative.