Check status of a running task. Poll until taskState is COMPLETE or FAILED. Use includeProcessDetails=true for step timing. taskId from run_* response.
AI agents call get_action_status 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.
This is a read-only operation that queries the status of an already-running task. It retrieves information about task progress and completion state without creating, modifying, deleting, or executing any operations. The tool merely provides visibility into asynchronous task execution initiated elsewhere.
From the tool's definition The tool description states 'Check status of a running task' and 'Poll until taskState is COMPLETE or FAILED', indicating retrieval and monitoring of existing task state with no modification or side effects.
Documented attack patterns abuse exactly the kind of access get_action_status 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 get_action_status:
{
"version": "1",
"default": "deny",
"tools": {
"get_action_status": {}
}
}get_action_status 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.
Check status of a running task. Poll until taskState is COMPLETE or FAILED. Use includeProcessDetails=true for step timing. taskId from run_* response. 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 get_action_status: 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.
get_action_status 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 get_action_status 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 get_action_status. 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.
get_action_status 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.