LeashIndex Get the report

Index / storage

Atono

io-atono-atono-mcp-server declares 42 capabilities across 42 tools, with 2 critical issues.

90/100 exposureHigh exposure

Manifest recorded 2026-10-11 from tools/list answered by the container image docker.io/atonoio/atono-mcp-server version 1.1.1 (published as the image docker.io/atonoio/atono-mcp-server:1.1.1, listed in the official MCP registry as io.atono/atono-mcp-server 1.1.1), run in an isolated container with no network access and placeholder credentials. The date changes only when the manifest does. Not verified by a maintainer.

Issues

These describe what this server's manifest declares. A product can provide controls that MCP has no way to express — token revocation, an admin console, audit logs — and this page cannot see them. The absence of a declaration is not evidence that a control is absent.

critical · irreversible-uncapped · 3 of 42 tools

3 tools are classified as irreversible and declare no limit.

critical · no-revocation · All 42 tools

42 of 42 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.

high · no-expiry · All 42 tools

42 of 42 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.

high · no-audit-trail · All 42 tools

42 of 42 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.

high · uncapped-write · 23 of 42 tools

23 tools can modify data and declare no limit.

low · uncapped-read · 16 of 42 tools

16 tools can read data and declare no limit.

Declared capabilities

How each tool was read. declared means the server's own annotation said so — self-reported and unverified. inferred is from the tool's name. assumed means nothing indicated either way.

ToolRead asBasis
atono_update_ai_contextdestructive declared
atono_get_ai_contextread declared
atono_upload_file_urlwrite inferred
atono_create_attachmentwrite inferred
atono_get_attachmentread declared
atono_get_bugread declared
atono_update_bug_stepwrite inferred
atono_update_bugwrite inferred
atono_document_bug_fixwrite inferred
atono_update_bug_assigneewrite inferred
atono_create_bugwrite inferred
atono_list_environmentsread declared
atono_create_epicwrite inferred
atono_list_epicsread declared
atono_get_epicread declared
atono_add_story_to_epicwrite inferred
atono_update_epic_titlewrite inferred
atono_update_epic_descriptionwrite inferred
atono_update_epic_user_storieswrite inferred
atono_remove_story_from_epicdelete inferred
atono_configurationread declared
atono_get_glossaryread declared
atono_get_storyread declared
atono_list_timebox_itemsread declared
atono_list_story_personasread declared
atono_create_storywrite inferred
atono_update_story_stepwrite inferred
atono_update_story_assigneewrite inferred
atono_update_story_acwrite inferred
atono_update_story_contentwrite inferred
atono_update_story_titlewrite inferred
atono_update_story_additional_contentwrite inferred
atono_update_story_teamwrite inferred
atono_link_bugs_or_storieswrite assumed
atono_get_subtasksread declared
atono_create_subtaskwrite inferred
atono_update_subtaskwrite inferred
atono_delete_subtaskdestructive declared
atono_list_timeboxesread declared
atono_list_teamsread declared
atono_get_team_workflowread declared
atono_list_usersread declared
Answering this question about your own agent? The self-serve stack report applies the same reading to your own stack or server and gives you a dated document you can hand to a customer's security review. It is generated in your browser, with nobody to wait for. Buying one does not change this page, its score or its place in the index — see Independence.
Maintain this server? If this page misreads your manifest, or your server has changed, submit its current tools/list response and it will be re-scored and dated. Corrections are published alongside the original, not in place of it.