List connected integration channels available for a public export flow. Use this before export_records for HubSpot deal exports. For MoneyForward/freee invoice_export workflows, use this only to discover accounting channel_id candidates when needed; preview_workflow/start_workflow with workflow_t...
AI agents call list_integration_channels to retrieve information from Sanka MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only query operation that retrieves a list of available integration channels. It has no side effects—it does not create, modify, delete, or execute any operations.
From the tool's definition The tool name is 'list_integration_channels' and the description states it 'List[s] connected integration channels available for a public export flow' and is used to 'discover' and 'preview' export options.
Attacks that exploit this kind of access
List connected integration channels available for a public export flow. Use this before export_records for HubSpot deal exports. For MoneyForward/freee invoice_export workflows, use this only to discover accounting channel_id candidates when needed; preview_workflow/start_workflow with workflow_type=invoice_export 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 MoneyForward/freee invoice_export 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →