list_recurring_events

List recurring event definitions. Returns recurring events sorted by modification date (newest first).

SERVERHuly SOURCE@firfi/huly-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-dearlordylord-huly-mcp/list-recurring-events.md

WHAT IT DOES

What list_recurring_events does on Huly

AI agents call list_recurring_events to retrieve information from Huly without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why list_recurring_events is rated Low

This tool retrieves and returns existing recurring event data without creating, modifying, deleting, or executing any operations. The use of 'List' and 'Returns' clearly identifies it as a read-only query operation.

From the tool's definition Tool name 'list_recurring_events' and description 'List recurring event definitions. Returns recurring events sorted by modification date (newest first)' indicate a retrieval/query operation with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_recurring_events safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Huly, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_recurring_events, this is the rule to start with:

list_recurring_events Allowed

list_recurring_events is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_recurring_events": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Huly, apply this rule, and every list_recurring_events call is checked against it from then on.

FAQ

Questions about list_recurring_events

What does the list_recurring_events tool do? +

List recurring event definitions. Returns recurring events sorted by modification date (newest first). It is categorised as a Read tool in the Huly MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_recurring_events? +

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

What risk level is list_recurring_events? +

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

Can I rate-limit list_recurring_events? +

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

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

list_recurring_events is provided by the Huly MCP server (@firfi/huly-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Huly, and thousands of servers like it.

This server

All 518 Huly tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →