Get the configuration of a task queue including rate limits and poller settings.
AI agents call temporal.task-queue.configuration to retrieve information from Temporal without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves configuration metadata about a task queue—rate limits and poller settings—without modifying infrastructure or triggering operations. It is a straightforward read operation with minimal blast radius if misused by an agent; the worst outcome would be information disclosure about internal queue tuning parameters.
From the tool's definition Tool name includes 'get' semantic (retrieve configuration); description states 'Get the configuration' with no mention of modification, deletion, or execution. Server description emphasizes 'read-only access'.
Documented attack patterns abuse exactly the kind of access temporal.task-queue.configuration gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Temporal, and nothing reaches the server without passing your rules. This is the rule we recommend for temporal.task-queue.configuration:
{
"version": "1",
"default": "deny",
"tools": {
"temporal.task-queue.configuration": {}
}
}temporal.task-queue.configuration 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.
Get the configuration of a task queue including rate limits and poller settings. It is categorised as a Read tool in the Temporal MCP Server, which means it retrieves data without modifying state.
Register the Temporal MCP server in PolicyLayer and add a rule for temporal.task-queue.configuration: 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 Temporal. Nothing to install.
temporal.task-queue.configuration 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 temporal.task-queue.configuration 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 temporal.task-queue.configuration. 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.
temporal.task-queue.configuration is provided by the Temporal MCP server (stevekinney/temporal-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Temporal, 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.
28 Temporal tools catalogued and risk-classified — across an index of 43,000+ MCP servers.