Open (wake up) a model. May return 202 if model is loading.
AI agents invoke open_model 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.
Opening/waking a model triggers an external operation on Anaplan's platform — it activates a model instance, which is a state change that initiates server-side processing. This is not a simple read (it changes the model's state from sleeping to active), not a write of data, and not destructive. It best fits Execute as it triggers an external operation whose effects depend on the model being targeted.
From the tool's definition Open (wake up) a model. May return 202 if model is loading.
Documented attack patterns abuse exactly the kind of access open_model 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 open_model:
{
"version": "1",
"default": "deny",
"tools": {
"open_model": {
"limits": [
{
"counter": "open_model_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} open_model 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.
Open (wake up) a model. May return 202 if model is loading. 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 open_model: 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.
open_model 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 open_model 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 open_model. 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.
open_model 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.