Get module details with default view dimension metadata (rows, columns, pages). The default viewId equals the moduleId -- use it with read_cells directly.
AI agents call show_moduledetails to retrieve information from Anaplan MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool is explicitly described as a getter that retrieves metadata about modules and their structure. There are no side effects, no data modification, no code execution, and no financial impact. This is a straightforward read operation typical of navigating a data model hierarchy.
From the tool's definition Tool performs 'Get module details' and retrieves 'default view dimension metadata (rows, columns, pages)' — purely data retrieval with no modification or execution capability.
Documented attack patterns abuse exactly the kind of access show_moduledetails 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 show_moduledetails:
{
"version": "1",
"default": "deny",
"tools": {
"show_moduledetails": {}
}
}show_moduledetails is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get module details with default view dimension metadata (rows, columns, pages). The default viewId equals the moduleId -- use it with read_cells directly. It is categorised as a Read tool in the Anaplan MCP MCP Server, which means it retrieves data without modifying state.
Register the Anaplan MCP server in PolicyLayer and add a rule for show_moduledetails: 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.
show_moduledetails is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the show_moduledetails 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 show_moduledetails. 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.
show_moduledetails 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.