Configure Memory
io-github-configure-dev-configure-memory 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.
2 tools are classified as irreversible and declare 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.
5 tools can modify data and declare no limit.
2 tools can read data and declare no limit.
Declared capabilities
| Tool | Read as | Basis |
|---|---|---|
configure_connect | write |
assumed |
configure_profile_read | read |
declared |
configure_profile_search | read |
declared |
configure_profile_remember | write |
assumed |
configure_profile_remember_many | write |
assumed |
configure_profile_forget | destructive |
declared |
configure_profile_commit | write |
inferred |
configure_project_share | destructive |
declared |
configure_profile_import | write |
assumed |
tools/list response and it will be re-scored and dated.
Corrections are published alongside the original, not in place of it.