Get the matching times for a schedule within a time range.
AI agents call temporal.schedule.matching-times 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 queries schedule data and returns matching times—a retrieval operation with no ability to modify, delete, or execute external operations. It fits the Read category as a data retrieval function. Severity is low because exposing schedule timing information has minimal risk; an agent cannot misuse this to cause significant harm.
From the tool's definition Tool name and description indicate it retrieves/queries matching times for a schedule within a time range. The verb 'get' and read-only server description confirm no side effects.
Documented attack patterns abuse exactly the kind of access temporal.schedule.matching-times 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.schedule.matching-times:
{
"version": "1",
"default": "deny",
"tools": {
"temporal.schedule.matching-times": {}
}
}temporal.schedule.matching-times 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 matching times for a schedule within a time range. 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.schedule.matching-times: 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.schedule.matching-times 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.schedule.matching-times 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.schedule.matching-times. 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.schedule.matching-times 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.