New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

calendars_add_calendar_to_schedule

Apply user availability schedule to a calendar

SERVERGhl SOURCE@aiwerk/mcp-server-ghl
Medium RISK CLASS
Category Write
Parameters 22 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/aiwerk-mcp-server-ghl/calendars-add-calendar-to-schedule.md

What calendars_add_calendar_to_schedule does on Ghl

AI agents use calendars_add_calendar_to_schedule to create or update resources in Ghl, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ghl environment.

ParameterTypeRequiredDescription
id string Yes Unique identifier of the schedule
calendarId string Yes Unique identifier of the team calendar to add to the schedule

Parameters from the server's own tool schema.

Why calendars_add_calendar_to_schedule is rated Medium

An AI agent can call calendars_add_calendar_to_schedule faster than any human can review: one bad instruction and it creates or modifies resources in Ghl by the hundred, each call as confident as the last.

Questions about calendars_add_calendar_to_schedule

What does the calendars_add_calendar_to_schedule tool do? +

Apply user availability schedule to a calendar. It is categorised as a Write tool in the Ghl MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does calendars_add_calendar_to_schedule accept? +

calendars_add_calendar_to_schedule accepts 2 parameters: id, calendarId. Required: id, calendarId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on calendars_add_calendar_to_schedule? +

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

What risk level is calendars_add_calendar_to_schedule? +

calendars_add_calendar_to_schedule is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit calendars_add_calendar_to_schedule? +

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

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

calendars_add_calendar_to_schedule is provided by the Ghl MCP server (@aiwerk/mcp-server-ghl). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Ghl, and thousands of servers like it.

This server

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Ghl's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.