Execute an export and return the data inline. Best for bulk reports across all products/customers/regions -- prefer this over calling read_cells in a loop. Handles the full run-wait-download lifecycle. Use show_exports first.
AI agents invoke run_export to trigger actions in Anaplan MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool executes a bulk export operation with lifecycle management (run-wait-download), which is an external operation triggered by the AI agent. While the operation itself is not destructive and is read-oriented in intent, the 'Execute' category applies because the tool actively runs/triggers processes rather than passively retrieving data.
From the tool's definition Tool name 'run_export' combined with description 'Execute an export and return the data inline' and 'Handles the full run-wait-download lifecycle' indicates this triggers external operations (export execution) whose effects depend on arguments (which data to…
Documented attack patterns abuse exactly the kind of access run_export gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Anaplan MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for run_export:
{
"version": "1",
"default": "deny",
"tools": {
"run_export": {
"limits": [
{
"counter": "run_export_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}run_export stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Execute an export and return the data inline. Best for bulk reports across all products/customers/regions -- prefer this over calling read_cells in a loop. Handles the full run-wait-download lifecycle. Use show_exports first. It is categorised as a Execute tool in the Anaplan MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Anaplan MCP server in PolicyLayer and add a rule for run_export: 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 Anaplan MCP. Nothing to install.
run_export is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the run_export 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 run_export. 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.
run_export is provided by the Anaplan MCP server (larasrinath/anaplan-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Anaplan MCP, 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.
70 Anaplan MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.