LeashIndex Get the report

Index / devtools

io.github.musepy/genable-mcp

io-github-musepy-genable-mcp declares 41 capabilities across 41 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.

88/100 exposureHigh exposure

Manifest recorded 2026-10-30 from tools/list answered by the npm package genable-mcp@0.1.3 (published to npm as genable-mcp, listed in the official MCP registry as io.github.musepy/genable-mcp 0.1.3), run in an isolated container with no network access and no 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 41 tools

41 of 41 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 · 1 of 41 tools

1 tool is classified as irreversible and declares no limit.

high · no-expiry · All 41 tools

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

41 of 41 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 · 28 of 41 tools

28 tools can modify data and declare no limit.

low · uncapped-read · 12 of 41 tools

12 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
jsxwrite inferred
inspectread inferred
describeread inferred
editwrite inferred
find_nodesread inferred
discover_propswrite assumed
replace_propsread inferred
find_referencesread inferred
delete_nodedelete inferred
move_nodewrite inferred
clone_nodewrite assumed
skillwrite assumed
stylewrite assumed
guidelinewrite assumed
helpread inferred
list_variablesread inferred
create_collectionwrite inferred
create_variablewrite inferred
ensure_collectionwrite assumed
ensure_variablewrite assumed
set_variable_valuewrite inferred
bind_variablewrite assumed
set_variable_modewrite inferred
create_componentwrite inferred
combine_componentswrite inferred
add_component_propwrite inferred
list_component_propsread inferred
create_instancewrite inferred
set_textwrite inferred
set_fillwrite inferred
set_strokewrite inferred
set_layoutwrite inferred
get_selectionread inferred
switch_pagewrite assumed
read_plugin_dataread inferred
write_plugin_datawrite inferred
create_vectorwrite inferred
get_screenshotread inferred
ask_userwrite assumed
subtaskwrite assumed
session_noteread 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.