LeashIndex Get the report

Index / devtools

io.github.laveeshb/logicapps-mcp

io-github-laveeshb-logicapps-mcp declares 40 capabilities across 40 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.

77/100 exposureHigh exposure

Manifest recorded 2026-10-27 from tools/list answered by the npm package logicapps-mcp@0.4.3 (published to npm as logicapps-mcp, listed in the official MCP registry as io.github.laveeshb/logicapps-mcp 0.4.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 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 · 2 of 40 tools

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

9 tools can modify data and declare no limit.

low · uncapped-read · 29 of 40 tools

29 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
list_subscriptionsread inferred
list_logic_appsread inferred
list_workflowsread inferred
get_workflow_definitionread inferred
get_workflow_triggersread inferred
list_run_historyread inferred
get_run_detailsread inferred
get_run_actionsread inferred
get_connectionsread inferred
create_connectionwrite inferred
get_connector_swaggerread inferred
invoke_connector_operationread inferred
get_host_statusread inferred
list_workflow_versionsread inferred
get_trigger_historyread inferred
get_action_repetitionsread inferred
get_action_request_historyread inferred
get_trigger_callback_urlread inferred
get_scope_repetitionsread inferred
get_expression_tracesread inferred
get_workflow_swaggerread inferred
get_action_ioread inferred
search_runsread inferred
get_workflow_versionread inferred
get_connection_detailsread inferred
test_connectionwrite assumed
enable_workflowwrite assumed
disable_workflowwrite assumed
run_triggerwrite assumed
cancel_rundelete inferred
resubmit_runwrite assumed
create_workflowwrite inferred
update_workflowwrite inferred
delete_workflowdelete inferred
clone_workflowwrite assumed
validate_clone_workflowread inferred
get_troubleshooting_guideread inferred
get_authoring_guideread inferred
get_referenceread inferred
get_workflow_instructionsread 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.