list_integration_channels
List connected integration channels available for a public export flow. Use this before export_records for supported HubSpot or NextEngine exports. For freee/MoneyForward invoice_export and QuickBooks Online invoice_export or bill_export workflows, use this only to discover accounting channel_id ...
This record as markdown: /tools/sankahq-sanka-mcp/list-integration-channels.md
What list_integration_channels does on Sanka MCP Server
AI agents call list_integration_channels to retrieve information from Sanka MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_integration_channels is rated Low
This tool retrieves and lists existing integration channel information to help determine which channels are available for export workflows. It is purely informational—it reads configuration data without modifying, executing, deleting, or committing financial transactions.
From the tool's definition Tool name is 'list_integration_channels' and description states it 'List connected integration channels available' and 'use this before export_records' and 'use this only to discover accounting channel_id candidates'.
Attacks that exploit this kind of access
The rule that runs list_integration_channels safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Sanka MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_integration_channels, this is the rule to start with:
list_integration_channels is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Sanka MCP Server, apply this rule, and every list_integration_channels call is checked against it from then on.
Questions about list_integration_channels
List connected integration channels available for a public export flow. Use this before export_records for supported HubSpot or NextEngine exports. For freee/MoneyForward invoice_export and QuickBooks Online invoice_export or bill_export workflows, use this only to discover accounting channel_id candidates; preview_workflow/start_workflow determines actual accounting export readiness. Do not treat integration-sync shadow_mode, rollout_stage, is_enabled, or outbound_pipeline_active fields from this endpoint as accounting workflow blockers. It is categorised as a Read tool in the Sanka MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Sanka MCP Server MCP server in PolicyLayer and add a rule for list_integration_channels: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Sanka MCP Server. Nothing to install.
list_integration_channels is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_integration_channels rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for list_integration_channels. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
list_integration_channels is provided by the Sanka MCP Server MCP server (sankahq/sanka-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Sanka MCP Server, and thousands of servers like it.
This server
Across the catalogue