io.github.theluckystrike/asset-register
io-github-theluckystrike-asset-register declares 9 capabilities across 9 tools, with 2 critical issues.
Issues
9 of 9 tools declare no way for the customer to switch them off once granted. This applies to every tool because MCP has no field in which to declare a revocation mechanism; the product may provide one outside MCP that a manifest cannot show.
1 tool is classified as irreversible and declares no limit.
9 of 9 tools declare no expiry. This applies to every tool because MCP has no field in which to declare an expiry; the product may provide one outside MCP that a manifest cannot show.
9 of 9 tools declare no record of their actions that the customer can read. This applies to every tool because MCP has no field in which to declare an audit requirement; the product may provide one outside MCP that a manifest cannot show.
4 tools can modify data and declare no limit.
4 tools can read data and declare no limit.
Declared capabilities
| Tool | Read as | Basis |
|---|---|---|
asset_add | write |
inferred |
asset_list | read |
declared |
asset_schedule | write |
assumed |
asset_journal | read |
inferred |
asset_dispose | write |
assumed |
asset_delete | destructive |
declared |
asset_report | read |
declared |
license_status | read |
declared |
license_activate | write |
assumed |
tools/list response and it will be re-scored and dated.
Corrections are published alongside the original, not in place of it.