build_recurrence_rule · Tick MCP: Risk & Policy

WHAT IT DOES

What build_recurrence_rule does on Tick

AI agents invoke build_recurrence_rule to trigger actions in Tick. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why build_recurrence_rule needs a policy

build_recurrence_rule triggers real processes with real consequences. An agent gone sideways doesn't fire it once — it starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

build_recurrence_rule Rate-limited

build_recurrence_rule stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "build_recurrence_rule": {
      "limits": [
        {
          "counter": "build_recurrence_rule_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Tick, so you can run agents against it safely.

FAQ

Questions about build_recurrence_rule

What does the build_recurrence_rule tool do? +

build_recurrence_rule. It is categorised as a Execute tool in the Tick MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on build_recurrence_rule? +

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

What risk level is build_recurrence_rule? +

build_recurrence_rule is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit build_recurrence_rule? +

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

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

build_recurrence_rule is provided by the Tick MCP server (kpihx/tick-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.