Low Risk

expand_rrule

Expand a recurrence rule (RRULE) into concrete event instances.

Part of the Temporal Cortex MCP server.

expand_rrule is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE TEMPORAL CORTEX MCP →

Free to start. No card required.

AI agents call expand_rrule to retrieve information from Temporal Cortex MCP without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though expand_rrule only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "expand_rrule": {}
  }
}

See the full Temporal Cortex MCP policy for all 12 tools.

Get this rule live on your own Temporal Cortex MCP server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY TEMPORAL CORTEX MCP →

View all 12 tools →

These attack patterns abuse exactly the kind of access expand_rrule gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so expand_rrule only ever does what you allow.

SECURE TEMPORAL CORTEX MCP →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the expand_rrule tool do? +

Expand a recurrence rule (RRULE) into concrete event instances.. It is categorised as a Read tool in the Temporal Cortex MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on expand_rrule? +

Register the Temporal Cortex MCP server in PolicyLayer and add a rule for expand_rrule: 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 Cortex MCP. Nothing to install.

What risk level is expand_rrule? +

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

Can I rate-limit expand_rrule? +

Yes. Add a rate_limit block to the expand_rrule 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 expand_rrule completely? +

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

expand_rrule is provided by the Temporal Cortex MCP server (temporal-cortex/cortex-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Temporal Cortex MCP tool call.

Deterministic rules across all 12 Temporal Cortex MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.