YAADMINCurrent inventory#
Endpoint inventory, software deployment and script execution through Action1.
16 static tools · Enabled by default
Permissions: action1.organizations.read, action1.endpoints.read, action1.software.read, action1.software.deploy, action1.software.uninstall, action1.scripts.read, action1.scripts.run, action1.powershell.run
Read-only Active Directory users, computers, groups and organizational units.
10 static tools · Enabled by default
Permissions: ad.health.read, ad.users.read, ad.computers.read, ad.groups.read, ad.ous.read
Per-user Codex App Server integration, opt-in, models and YAADMIN tool bridging.
1 static registration · Disabled by default
Permissions: codex.use, codex.manage
Owner-scoped file creation, reading and stored-table queries.
3 static tools · Enabled by default
Permissions: files.create, files.upload, files.read, files.delete
Discover and invoke tools from configured external MCP servers.
Dynamic MCP tools · Enabled by default
Permissions: mcp.use (fallback); per-tool permissions are discovered dynamically.
Read-only 1C HTTP service queries, nomenclature, stock and movements.
11 static tools · Enabled by default
Permissions: onec.schema.read, onec.query.read, onec.health.read, onec.warehouses.read, onec.nomenclature.read, onec.images.read, onec.document_text.read, onec.search.read, onec.stock.read, onec.movements.read
Resolve named infrastructure targets using connected providers.
1 static registration · Enabled by default
Permissions: targets.resolve
How modules fit#
Modules declare metadata and register tools through the registry. The manager validates capabilities, persists desired enabled state and coordinates loading/unloading. External packages enter discovery through generic entrypoints.
Tools and permissions#
The static inventory contains 42 registrations. Codex bootstrap is disabled/internal; MCP tools are discovered dynamically and are not counted as permanent static registrations. Exact tool counts do not guarantee successful configuration or provider connectivity.
Health and diagnostics#
Module administration exposes settings, health and diagnostic detail. Action1, AD, 1C and MCP have backend health; other modules may report loaded state without a provider health check. Do not assume a universal custom diagnostics hook.
Integration scope#
Native RAS, Terminal Server, Dahua/Video, U-Prox and n8n modules are not verified in this snapshot. They can be considered custom/external integration possibilities only when a real implementation exposes the required tools.
Continue with Install modules or Develop a module.