Low Risk

get_lists

Retrieve user lists

How to control get_lists ↓

What get_lists does on Iterable MCP Server

AI agents call get_lists to retrieve information from Iterable MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why get_lists needs a policy

The tool purely retrieves/queries existing user list data from the Iterable marketing platform. There is no creation, modification, deletion, or execution involved. This is a standard Read category operation with low severity since it only accesses data without altering state or enabling harmful actions.

From the tool's definition Tool name is 'get_lists' and description states 'Retrieve user lists' — this is a data retrieval operation with no modification or side effects.

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

How to control get_lists

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_lists:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_lists": {}
  }
}

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

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

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_lists

What does the get_lists tool do? +

Retrieve user lists. 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_lists? +

Register the Iterable MCP Server MCP server in PolicyLayer and add a rule for get_lists: 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_lists? +

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

Can I rate-limit get_lists? +

Yes. Add a rate_limit block to the get_lists 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_lists completely? +

Set action: deny in the PolicyLayer policy for get_lists. 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_lists? +

get_lists 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.

Free to start. No card required.

78 Iterable MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.