List all currently in-progress (RUNNING) async requests across your TMS account. Use for monitoring bulk background operations. To check a specific request by ID, use tms_get_async_request instead. (GET /api2/v1/async)
AI agents call tms_list_pending_requests to retrieve information from Phrase without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries the status of asynchronous requests without creating, modifying, or deleting any data. It is purely observational for monitoring purposes, fitting squarely within the Read category with low severity due to its non-invasive nature.
From the tool's definition Tool description explicitly states 'List all currently in-progress (RUNNING) async requests' and notes 'Use for monitoring bulk background operations.' The endpoint is GET /api2/v1/async, a read-only HTTP method with no data modification.
Attacks that exploit this kind of access
List all currently in-progress (RUNNING) async requests across your TMS account. Use for monitoring bulk background operations. To check a specific request by ID, use tms_get_async_request instead. (GET /api2/v1/async). It is categorised as a Read tool in the Phrase MCP Server, which means it retrieves data without modifying state.
Register the Phrase MCP server in PolicyLayer and add a rule for tms_list_pending_requests: 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 Phrase. Nothing to install.
tms_list_pending_requests 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 tms_list_pending_requests 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 tms_list_pending_requests. 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.
tms_list_pending_requests is provided by the Phrase MCP server (phrase-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →