Start a large volume list read (for lists too large for get_list_items). Lifecycle: create -> poll with get_list_readrequest -> download pages with get_list_readrequest_page -> cleanup with delete_list_readrequest.
AI agents invoke create_list_readrequest 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.
This tool initiates an asynchronous read operation on the Anaplan server. While the intent is read-only (retrieving list data), it 'starts' an external operation/task that must be polled and managed through a lifecycle, making it Execute rather than a simple Read. The blast radius is low since it only retrieves data and does not modify or delete anything.
From the tool's definition 'Start a large volume list read' and 'Lifecycle: create -> poll with get_list_readrequest -> download pages -> cleanup' — initiates an async read operation that triggers external processing
Documented attack patterns abuse exactly the kind of access create_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 create_list_readrequest:
{
"version": "1",
"default": "deny",
"tools": {
"create_list_readrequest": {
"limits": [
{
"counter": "create_list_readrequest_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}create_list_readrequest 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.
Start a large volume list read (for lists too large for get_list_items). Lifecycle: create -> poll with get_list_readrequest -> download pages with get_list_readrequest_page -> cleanup with delete_list_readrequest. 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 create_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.
create_list_readrequest 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 create_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 create_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.
create_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.