Delete a large volume list read request to free server resources. Always call this after downloading all pages.
AI agents call delete_list_readrequest 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.
This tool irreversibly removes a list read request object. While the impact is scoped to cleaning up temporary resources (not core business data), the action cannot be undone and represents a destructive operation.
From the tool's definition Tool name explicitly contains 'delete'; description states 'Delete a large volume list read request' with emphasis on cleanup of server resources. The action is irreversible—once deleted, the read request and its associated state are removed.
Documented attack patterns abuse exactly the kind of access delete_list_readrequest 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 delete_list_readrequest:
{
"version": "1",
"default": "deny",
"hide": [
"delete_list_readrequest"
]
} delete_list_readrequest 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.
Delete a large volume list read request to free server resources. Always call this after downloading all pages. 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 delete_list_readrequest: 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.
delete_list_readrequest 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 delete_list_readrequest 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 delete_list_readrequest. 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.
delete_list_readrequest 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.