Get the job status and download URLs for files from a completed export job. Files are added to the list as the export job runs. Use
AI agents call get_export_files 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.
This tool retrieves status information and URLs from an already-completed export job. It performs a query operation that returns data without creating, modifying, deleting, or executing any actions. The operation is idempotent and has no side effects on the underlying data or system state.
From the tool's definition Tool description states 'Get the job status and download URLs for files from a completed export job.' The verb 'Get' and the retrieval of status/URLs indicate read-only data access with no modifications or side effects.
Documented attack patterns abuse exactly the kind of access get_export_files gives an agent:
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_export_files:
{
"version": "1",
"default": "deny",
"tools": {
"get_export_files": {}
}
}get_export_files is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get the job status and download URLs for files from a completed export job. Files are added to the list as the export job runs. Use. It is categorised as a Read tool in the Iterable MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Iterable MCP Server MCP server in PolicyLayer and add a rule for get_export_files: 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.
get_export_files 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 get_export_files 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 get_export_files. 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.
get_export_files 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.
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.