get_channels

THE RISK

Low Risk

Why get_channels needs a policy

This tool retrieves information about available communication channels without any side effects, data modification, or external operations. It is a simple query operation that provides read-only access to channel configuration metadata.

From the tool's definition Tool name 'get_channels' and description 'Get all available communication channels' indicate a retrieval operation with no modification of data.

Documented attack patterns abuse exactly the kind of access get_channels gives an agent:

POLICY

How to control get_channels

PolicyLayer is an MCP gateway — it sits between your AI agents and Iterable MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_channels:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_channels": {}
  }
}

get_channels is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Iterable MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Iterable MCP Server tools

Destructive bulk_delete_catalog_items Bulk delete catalog items by their IDs Destructive cancel_campaign Cancel a scheduled or recurring campaign Destructive cancel_export_job Cancel a queued or running export job created with Destructive delete_catalog Delete a catalog Destructive delete_catalog_item Delete a specific catalog item by ID Destructive delete_list Delete a user list Destructive delete_snippet Delete a snippet by ID (numeric) or name (string) Destructive delete_templates Delete one or more templates by ID

All 78 Iterable MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get_channels

What does the get_channels tool do? +

Get all available communication channels (email, SMS, push, etc.). It is categorised as a Read tool in the Iterable MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_channels? +

Register the Iterable MCP Server MCP server in PolicyLayer and add a rule for get_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 Iterable MCP Server. Nothing to install.

What risk level is get_channels? +

get_channels is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_channels? +

Yes. Add a rate_limit block to the get_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.

How do I block get_channels completely? +

Set action: deny in the PolicyLayer policy for get_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.

What MCP server provides get_channels? +

get_channels is provided by the Iterable MCP Server MCP server (iterable/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Iterable MCP Server tool call.

Start from Iterable MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →