Update fiscal year for model calendar (WARNING: may affect time ranges). Use show_modelcalendar to see the current value first.
AI agents use set_fiscalyear to create or update resources in Anaplan MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Anaplan MCP environment.
This tool creates or modifies calendar configuration data in Anaplan. While the change can technically be reversed (update to a different fiscal year), it impacts time-based calculations and reporting across an entire model, making it a high-severity Write operation. It is not Destructive because fiscal year changes are reversible and do not irreversibly delete data.
From the tool's definition set_fiscalyear updates fiscal year for model calendar. The description explicitly warns it 'may affect time ranges', indicating reversible but impactful data modification across the model.
Documented attack patterns abuse exactly the kind of access set_fiscalyear 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_fiscalyear:
{
"version": "1",
"default": "deny",
"tools": {
"set_fiscalyear": {
"limits": [
{
"counter": "set_fiscalyear_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} set_fiscalyear stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Update fiscal year for model calendar (WARNING: may affect time ranges). Use show_modelcalendar to see the current value first. It is categorised as a Write tool in the Anaplan MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Anaplan MCP server in PolicyLayer and add a rule for set_fiscalyear: 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_fiscalyear is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the set_fiscalyear 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_fiscalyear. 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_fiscalyear 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.