list_event_instances

List instances of a recurring event. Returns instances sorted by date. Supports filtering by date range. Use includeParticipants=true to fetch full participant info (extra lookups).

SERVERHuly SOURCEdugynoo/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/dugynoo-huly-mcp/list-event-instances.md

WHAT IT DOES

What list_event_instances does on Huly

AI agents call list_event_instances 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_event_instances is rated Low

This tool retrieves and lists calendar event instances with optional date filtering. It performs data retrieval only (including optional participant lookups) without creating, modifying, deleting, or executing any operations. This is a straightforward Read operation with minimal security risk.

From the tool's definition Tool name 'list_event_instances' and description 'List instances of a recurring event. Returns instances sorted by date. Supports filtering by date range.' — retrieves/queries calendar event data with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_event_instances 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_event_instances, this is the rule to start with:

list_event_instances Allowed

list_event_instances 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_event_instances": {}
  }
}

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_event_instances call is checked against it from then on.

FAQ

Questions about list_event_instances

What does the list_event_instances tool do? +

List instances of a recurring event. Returns instances sorted by date. Supports filtering by date range. Use includeParticipants=true to fetch full participant info (extra lookups). 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_event_instances? +

Register the Huly MCP server in PolicyLayer and add a rule for list_event_instances: 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_event_instances? +

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

Can I rate-limit list_event_instances? +

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

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

list_event_instances is provided by the Huly MCP server (dugynoo/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 218 Huly tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server →get_event_details on CTFtime MCP Server → The MCP Attack Database →

Guides

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