Set current period for a model (WARNING: may cause data loss if periods are removed). Use show_currentperiod to see the current value first.
AI agents call set_currentperiod to permanently remove resources in Anaplan MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool modifies the current period setting of a model, and the description explicitly warns of potential data loss if periods are removed as a result. This makes it destructive in nature — the data loss is irreversible. The severity is high because misconfiguring the current period across a model could corrupt or permanently lose time-series data at scale.
From the tool's definition WARNING: may cause data loss if periods are removed
Documented attack patterns abuse exactly the kind of access set_currentperiod 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 set_currentperiod:
{
"version": "1",
"default": "deny",
"hide": [
"set_currentperiod"
]
} set_currentperiod disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Set current period for a model (WARNING: may cause data loss if periods are removed). Use show_currentperiod to see the current value first. It is categorised as a Destructive tool in the Anaplan MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Anaplan MCP server in PolicyLayer and add a rule for set_currentperiod: 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.
set_currentperiod is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the set_currentperiod 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 set_currentperiod. 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.
set_currentperiod 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.