As opposed to throwing a hissy fit because I've not taken time out of my busy day to fill out forms in whatever third rate piece of junk project management "tool" they've adopted so they can just run a report and pretend they've done their job.
Ignoring that though, I'd say, if anything, Agile promotes using simple tools like wallboards (physical wallboards, with physical cards). I don't really think you can pin using a bad tool on the Agile community when they largely prefer not to use these tools in the first place.
I absolutely can pin it on the agile community, because if you take the Agile argument away from them, they're left defending a crappy tool with no arguments at all.
As a bug-tracker shoehorned into doing double duty as a Kanban board, does Jira have rough edges? Sure.
However, used as a slightly more feature-full variant of Trello, as a wall of virtual sticky-notes, as a way to help see if the team improves over time like it should, it's pretty useful.
The moment it becomes an impediment it, well, is an impediment, and should be dealt with accordingly.
They exist in all walks of life and all project processes. Agile is not immune from this, but nor it it any worse.
I would agree that anyone who blindly follows what someone else has written in a book without bothering to consider whether you really understand it, whether it actually makes sense, and whether it needs to be modified to suit your particular circumstances is clearly not much of a thinker.
But taking and developing ideas originated elsewhere doesn't seem an intrinsically bad thing to be doing.
The latter is riddled with "process" and is just as bad as waterfall.
The former is a hodgepodge of "whatever has in the past worked for this team and was flexible enough to keep everyone happy while letting us have a modicum of an idea what stage the project is in".
You want to work on the latter. Because it doesn't matter what you call your methodology, what matters is that it works and that issues users care about get fixed.