Actora Tenant — Hosted Chat, Tasks & Usage
io-github-sftgroup-actora-tenant declares 9 capabilities across 9 tools, with 2 critical issues. One of them, no-revocation, is recorded for every server in the index because MCP has no field in which to declare a way to switch a tool off; a missing declaration is not evidence that the control is missing.
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 annotated by the server as destructive (destructiveHint) and declares no limit. In MCP that annotation marks a tool that may make destructive changes rather than only additive ones; it does not say the change cannot be undone.
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.
3 tools can modify data and declare no limit.
5 tools can read data and declare no limit.
Declared capabilities
| Tool | Read as | Basis |
|---|---|---|
actora_gateway_tenant | read |
declared |
actora_gateway_chat | write |
assumed |
actora_gateway_create_session | write |
inferred |
actora_gateway_create_task | write |
inferred |
actora_gateway_get_task | read |
declared |
actora_gateway_list_tasks | read |
declared |
actora_gateway_cancel_task | destructive |
declared |
actora_tenant_plans | read |
declared |
actora_tenant_usage | read |
declared |
tools/list response and it will be re-scored and dated.
Corrections are published alongside the original, not in place of it.