This record as markdown: /tools/delano-postman-mcp-server/get-task-status.md
What get_task_status does on Postman
AI agents call get_task_status to retrieve information from Postman without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_task_status is rated Low
This tool retrieves the status of an existing asynchronous task. It performs a read-only query with no side effects, no data modification, and no execution of external operations. The blast radius of misuse is minimal—an agent could only retrieve status information it should not see, not modify or delete anything.
From the tool's definition Tool name 'get_task_status' and description 'Get status of an asynchronous task' indicate a query operation that retrieves status information without modifying any data.
Attacks that exploit this kind of access
The rule that runs get_task_status safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Postman, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_task_status, this is the rule to start with:
get_task_status is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Postman, apply this rule, and every get_task_status call is checked against it from then on.
Questions about get_task_status
Get status of an asynchronous task. It is categorised as a Read tool in the Postman MCP Server, which means it retrieves data without modifying state.
Register the Postman MCP server in PolicyLayer and add a rule for get_task_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 Postman. Nothing to install.
get_task_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_task_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_task_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_task_status is provided by the Postman MCP server (delano/postman-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Postman, and thousands of servers like it.
This server
Across the catalogue