LeashIndex Get the report

Index / devtools

io.github.sergii-ziborov/weavatrix-refactor-js

io-github-sergii-ziborov-weavatrix-refactor-js declares 45 capabilities across 45 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.

90/100 exposureHigh exposure

Manifest recorded 2026-11-04 from tools/list answered by the npm package weavatrix-refactor-js@0.1.6 (published to npm as weavatrix-refactor-js, listed in the official MCP registry as io.github.sergii-ziborov/weavatrix-refactor-js 0.1.6), 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 45 tools

45 of 45 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 · 3 of 45 tools

3 tools are classified as irreversible and declare no limit.

high · no-expiry · All 45 tools

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

45 of 45 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 · 21 of 45 tools

21 tools can modify data and declare no limit.

low · uncapped-read · 21 of 45 tools

21 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
graph_statsread inferred
get_noderead inferred
get_neighborsread inferred
query_graphread inferred
god_nodeswrite assumed
shortest_pathread inferred
get_dependentsread inferred
change_impactwrite assumed
git_historyread inferred
verified_changewrite inferred
trace_api_contractwrite assumed
get_communityread inferred
search_coderead inferred
read_sourceread inferred
inspect_symbolread inferred
context_bundleread inferred
find_duplicatesread inferred
find_dead_coderead inferred
run_auditwrite assumed
coverage_mapwrite assumed
hot_path_reviewwrite assumed
list_communitiesread inferred
module_mapread inferred
list_endpointsread inferred
trace_endpointwrite assumed
rebuild_graphwrite assumed
graph_diffwrite assumed
get_architecture_contractread inferred
prepare_changewrite inferred
verify_architectureread inferred
explain_architecture_violationread inferred
propose_architecture_exceptionwrite assumed
open_repowrite assumed
list_known_reposread inferred
apply_edit_planwrite inferred
rollback_last_applywrite inferred
rename_symbolwrite inferred
rename_related_symbolswrite inferred
move_filewrite inferred
move_symbolwrite inferred
delete_readinessdelete inferred
change_signaturedelete inferred
edit_symbolwrite inferred
bulk_replacewrite assumed
organize_importsdelete 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.