LeashIndex Get the report

Index / devtools

Relm CRM

com-relmcrm-relm declares 41 capabilities across 41 tools, with 2 critical issues.

96/100 exposureHigh exposure

Manifest recorded 2026-10-11 from tools/list on https://api.relmcrm.com/mcp, published in the official MCP registry as com.relmcrm/relm 0.17.1. 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 · 11 of 41 tools

11 tools are classified as irreversible and declare 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 · 13 of 41 tools

13 tools can modify data and declare no limit.

low · uncapped-read · 17 of 41 tools

17 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
relm_describe_schemaread declared
relm_searchread declared
relm_listread declared
relm_getread declared
relm_createwrite inferred
relm_updatewrite inferred
relm_deletedestructive declared
relm_restoredelete inferred
relm_log_activitysend inferred
relm_list_pipelinesread declared
relm_create_pipelinewrite inferred
relm_manage_stagedestructive declared
relm_create_typewrite inferred
relm_create_fieldwrite inferred
relm_create_enum_valuewrite inferred
relm_batchdestructive declared
relm_automations_capabilitiesread declared
relm_connect_channelsend inferred
relm_list_connectionsread declared
relm_create_automationwrite inferred
relm_list_automationsread declared
relm_create_templatewrite inferred
relm_list_templatesread declared
relm_create_sequencewrite inferred
relm_list_sequencesread declared
relm_preview_sequenceread declared
relm_enrollwrite assumed
relm_create_webhookwrite inferred
relm_list_webhooksread declared
relm_delete_webhookdestructive declared
relm_get_automationread declared
relm_get_sequenceread declared
relm_get_pipelineread declared
relm_get_webhookread declared
relm_manage_automationdestructive declared
relm_manage_sequencedestructive declared
relm_manage_pipelinedestructive declared
relm_manage_webhookwrite assumed
relm_delete_connectiondestructive declared
relm_get_usageread declared
relm_set_spend_capwrite 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.