build_ics_event
utilpeek: Build an iCalendar file from JSON events. To read an .ics file use parse_ics. Returns RFC 5545 VCALENDAR text built from 1-50 events, CRLF lines folded at 75 octets and text escaped, with its base64, a data: URI and the uids. Input: events, optional calendar_name, default timezone and t...
This record as markdown: /tools/dev-tanod-tanod/build-ics-event.md
What build_ics_event does on Tanod
AI agents invoke build_ics_event to trigger actions in Tanod. 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
events | array | Yes | 1-50 events. |
timezone | object | — | Default IANA time zone for events without one. |
time_format | string | — | tzid (default): zoned times as TZID=...; utc: all times in UTC. |
calendar_name | object | — | Calendar name (X-WR-CALNAME). |
Parameters from the server's own tool schema.
Why build_ics_event is rated High
build_ics_event 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
The rule that runs build_ics_event safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Tanod, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For build_ics_event, this is the rule to start with:
build_ics_event 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Tanod, apply this rule, and every build_ics_event call is checked against it from then on.
Questions about build_ics_event
utilpeek: Build an iCalendar file from JSON events. To read an .ics file use parse_ics. Returns RFC 5545 VCALENDAR text built from 1-50 events, CRLF lines folded at 75 octets and text escaped, with its base64, a data: URI and the uids. Input: events, optional calendar_name, default timezone and time_format. Pure computation: no network access, nothing stored. A zoned start is written as TZID=<IANA name> with no VTIMEZONE block; an offset becomes UTC; a plain local time stays floating. All-day end is the last day, inclusive. A bad time zone, date, rrule, email or url, or both end and duration, is a 422 naming the event (not charged). Typically under 0.1 s. Price: USD 0.001. Free: 10 utilpeek calls per IP per UTC day. Docs: https://tanod.dev/learn/ics-calendar-api.html. It is categorised as a Execute tool in the Tanod MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
build_ics_event accepts 4 parameters: events, timezone, time_format, calendar_name. Required: events. The full parameter table on this page comes from the server's own tool schema.
Register the Tanod MCP server in PolicyLayer and add a rule for build_ics_event: 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 Tanod. Nothing to install.
build_ics_event is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the build_ics_event 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 build_ics_event. 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.
build_ics_event is provided by the Tanod MCP server (https://tanod.dev/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Tanod, and thousands of servers like it.
Across the catalogue