LeashIndex Get the report

Index / storage

Backblaze B2 MCP Server

io-github-backblaze-labs-b2-mcp declares 40 capabilities across 40 tools, with 2 critical issues.

97/100 exposureHigh exposure

Manifest recorded 2026-10-15 from tools/list answered by the npm package @backblaze-labs/b2-mcp@0.2.2 (published to npm as @backblaze-labs/b2-mcp, listed in the official MCP registry as io.github.backblaze-labs/b2-mcp 0.2.2), 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 · no-revocation · All 40 tools

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

critical · irreversible-uncapped · 15 of 40 tools

15 tools are classified as irreversible and declare no limit.

high · no-expiry · All 40 tools

40 of 40 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 40 tools

40 of 40 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 · 6 of 40 tools

6 tools can modify data and declare no limit.

low · uncapped-read · 19 of 40 tools

19 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
b2_authorize_accountread declared
b2_create_bucketwrite inferred
b2_create_group_memberdestructive declared
b2_create_keydestructive declared
b2_delete_bucketdestructive declared
b2_delete_keydestructive declared
b2_eject_group_memberdestructive declared
b2_get_bucket_notification_rulesread declared
b2_list_bucketsread declared
b2_list_group_membersread declared
b2_list_groupsread declared
b2_list_keysread declared
b2_list_largest_filesread declared
b2_rank_egress_leadersread declared
b2_report_usage_growthread declared
b2_reserve_trial_create_accountdestructive declared
b2_set_bucket_notification_rulesdestructive declared
b2_unfinished_uploadsread declared
b2_update_bucketdestructive declared
b2_update_file_legal_holddestructive declared
b2_update_file_retentiondestructive declared
s3_abort_multipart_uploaddestructive declared
s3_complete_multipart_uploadwrite inferred
s3_copy_objectwrite assumed
s3_create_multipart_uploadwrite inferred
s3_delete_objectdestructive declared
s3_delete_objectsdestructive declared
s3_get_bucket_locationread declared
s3_get_objectread inferred
s3_get_presigned_upload_part_urlread inferred
s3_get_presigned_urldestructive declared
s3_head_bucketread declared
s3_head_objectread declared
s3_list_multipart_uploadsread declared
s3_list_object_versionsread declared
s3_list_objects_v2read declared
s3_list_partsread declared
s3_put_bucket_lifecycledestructive declared
s3_put_objectwrite inferred
s3_upload_part_copywrite inferred
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.