tms_get_async_limits

Check the async request quota: how many concurrent async operations are allowed and how many are currently in use. Call this before triggering a large number of async exports to avoid hitting rate limits. (GET /api2/v1/async/status)

Server Phrase phrase-mcp-server
Category Read
Risk class Low
Parameters 00 required

What tms_get_async_limits does on Phrase

AI agents call tms_get_async_limits 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.

Why tms_get_async_limits needs a policy

This tool performs a read-only query against the Phrase API's async status endpoint. It retrieves quota information without modifying, executing operations, or causing destructive changes. The low severity reflects that misuse would only expose usage metrics, with no blast radius for unintended operations.

From the tool's definition Tool description states it "Check[s] the async request quota" and "how many concurrent async operations are allowed and how many are currently in use" — purely informational retrieval via GET endpoint with no side effects.

Questions about tms_get_async_limits

What does the tms_get_async_limits tool do? +

Check the async request quota: how many concurrent async operations are allowed and how many are currently in use. Call this before triggering a large number of async exports to avoid hitting rate limits. (GET /api2/v1/async/status). It is categorised as a Read tool in the Phrase MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on tms_get_async_limits? +

Register the Phrase MCP server in PolicyLayer and add a rule for tms_get_async_limits: 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.

What risk level is tms_get_async_limits? +

tms_get_async_limits is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit tms_get_async_limits? +

Yes. Add a rate_limit block to the tms_get_async_limits 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.

How do I block tms_get_async_limits completely? +

Set action: deny in the PolicyLayer policy for tms_get_async_limits. 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.

What MCP server provides tms_get_async_limits? +

tms_get_async_limits 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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.