LeashIndex Get the report

Index / devtools

io.github.sandeepbazar/ocm-mcp-server

io-github-sandeepbazar-ocm-mcp-server declares 35 capabilities across 35 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.

73/100 exposureHigh exposure

Manifest recorded 2026-11-04 from tools/list answered by the PyPI package ocm-mcp-server==0.4.0 (published to PyPI as ocm-mcp-server, listed in the official MCP registry as io.github.sandeepbazar/ocm-mcp-server 0.4.0), 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 35 tools

35 of 35 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 · destructive-uncapped · 3 of 35 tools

3 tools are annotated by the server as destructive (destructiveHint) and declare no limit. In MCP that annotation marks a tool that may make destructive changes rather than only additive ones; it does not say the change cannot be undone.

high · no-expiry · All 35 tools

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

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

3 tools can modify data and declare no limit.

low · uncapped-read · 29 of 35 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_clustersread declared
get_clusterread declared
list_cluster_setsread declared
list_cluster_set_bindingsread declared
list_cluster_claimsread declared
get_cluster_inforead declared
get_cluster_healthread declared
get_fleet_healthread declared
query_eventsread declared
get_pod_logsread declared
list_placementsread declared
get_placement_decisionread declared
list_addon_placement_scoresread declared
list_manifestworksread declared
get_manifestworkread declared
list_manifestworkreplicasetsread declared
propose_manifestworkwrite assumed
apply_manifestworkdestructive declared
propose_rollbackwrite assumed
rollback_manifestworkdestructive declared
list_cluster_management_addonsread declared
get_addon_healthread declared
list_addons_for_clusterread declared
list_pending_csrsread declared
propose_cluster_actionwrite assumed
apply_cluster_actiondestructive declared
list_policiesread declared
list_policy_violationsread declared
list_hosted_clustersread declared
get_hosted_clusterread declared
list_node_poolsread declared
list_resourcesread declared
get_resourceread declared
list_pending_proposalsread declared
get_audit_trailread 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.