Execute a process (chain of imports/exports/deletes). Use mappingParameters to target a specific dimension at runtime. Use show_processes first. Monitor with get_action_status; download_processdump for failures.
AI agents invoke run_process 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 triggers execution of predefined processes that can include imports, exports, and deletes—operations whose effects depend entirely on what process is configured at runtime. The ability to execute chains of operations, particularly those including deletes, qualifies this as Execute rather than Write.
From the tool's definition Tool description states 'Execute a process (chain of imports/exports/deletes)' and explicitly mentions it runs transactional operations including deletes. The name 'run_process' and verb 'Execute' indicate active invocation of external workflows.
Documented attack patterns abuse exactly the kind of access run_process 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_process:
{
"version": "1",
"default": "deny",
"tools": {
"run_process": {
"limits": [
{
"counter": "run_process_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}run_process 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 a process (chain of imports/exports/deletes). Use mappingParameters to target a specific dimension at runtime. Use show_processes first. Monitor with get_action_status; download_processdump for failures. 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_process: 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_process 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_process 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_process. 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_process 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.