Get the worker versioning rules for a task queue, including assignment and redirect rules.
AI agents call temporal.worker.versioning-rules 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 data (worker versioning rules) for a task queue without modifying, executing, or deleting anything. It is a straightforward read operation consistent with the read-only nature of the entire Temporal MCP server. Low severity reflects minimal blast radius—misuse would only expose infrastructure metadata, not cause operational impact.
From the tool's definition Tool name includes 'Get' operation pattern; description states 'Get the worker versioning rules' which is a retrieval operation with no modification capability. Server description explicitly states 'read-only access'.
Documented attack patterns abuse exactly the kind of access temporal.worker.versioning-rules 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.worker.versioning-rules:
{
"version": "1",
"default": "deny",
"tools": {
"temporal.worker.versioning-rules": {}
}
}temporal.worker.versioning-rules 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 worker versioning rules for a task queue, including assignment and redirect rules. 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.worker.versioning-rules: 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.worker.versioning-rules 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.worker.versioning-rules 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.worker.versioning-rules. 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.worker.versioning-rules 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.