Check the current concurrent call limits and usage for your account.
AI agents call retell_get_concurrency to retrieve information from Retell AI MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only reads and returns information about current concurrency limits and usage metrics. It performs no side effects, does not modify data, execute code, delete resources, or commit financial transactions. It is a simple informational query matching the 'Read' category pattern of retrieving or querying data.
From the tool's definition Tool name 'retell_get_concurrency' and description 'Check the current concurrent call limits and usage for your account' indicate a query operation that retrieves account status information without modifying state.
Attacks that exploit this kind of access
Check the current concurrent call limits and usage for your account. It is categorised as a Read tool in the Retell AI MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Retell AI MCP Server MCP server in PolicyLayer and add a rule for retell_get_concurrency: 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 Retell AI MCP Server. Nothing to install.
retell_get_concurrency 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 retell_get_concurrency 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 retell_get_concurrency. 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.
retell_get_concurrency is provided by the Retell AI MCP Server MCP server (itsanamune/retellsimp). 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 →