Critical-risk tools in Aidex
4 of the 29 tools in Aidex are classified as critical risk. This page profiles those tools specifically, with recommended policy actions and the attack patterns that target them.
Every operation listed below is an action PolicyLayer recommends controlling at the transport layer. Open any tool to see the full profile, risk score, and YAML policy snippet.
Tools at critical risk
-
aidex_logDestructive 5/5Universal Log Hub — receive and query logs from any external program (C#, Python, Node, etc.) via HTTP. Zero-cost when not used. Actions: init (start HTTP server), free (stop se...
-
aidex_removeDestructive 5/5Remove a file from the AiDex index. Use when a file has been deleted from the project.
-
aidex_taskDestructive 5/5Manage a single task in the project backlog. Actions: create (new task), read (get task + log), update (change fields), delete, log (add history note). Tasks persist in the AiDe...
-
aidex_unlinkDestructive 5/5Remove a linked dependency project.
Attacks that target this class
Critical-risk tools in any server share these documented attack patterns. Each links to the full case and the defensive policy.
More on Aidex
Enforce policy on Aidex
One command generates a policy scaffold for every server in your MCP config.
npx -y @policylayer/intercept init