This record as markdown: /tools/io-github-heznpc-iconnect/gws-calendar-create.md
What gws_calendar_create does on Iconnect
AI agents use gws_calendar_create to create or update resources in Iconnect, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Iconnect environment.
Why gws_calendar_create is rated Medium
This tool creates calendar events, which is a reversible write operation—events can be edited or deleted later. It does not delete data (would be Destructive), execute arbitrary code (would be Execute), or commit financial obligations (would be Financial).
From the tool's definition Tool name 'gws_calendar_create' and description 'Create an event in Google Calendar' explicitly indicate a create operation that modifies calendar data reversibly.
Attacks that exploit this kind of access
The rule that runs gws_calendar_create safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Iconnect, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For gws_calendar_create, this is the rule to start with:
gws_calendar_create stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Iconnect, apply this rule, and every gws_calendar_create call is checked against it from then on.
Questions about gws_calendar_create
Create an event in Google Calendar. It is categorised as a Write tool in the Iconnect MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Iconnect MCP server in PolicyLayer and add a rule for gws_calendar_create: 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 Iconnect. Nothing to install.
gws_calendar_create is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the gws_calendar_create 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 gws_calendar_create. 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.
gws_calendar_create is provided by the Iconnect MCP server (iconnect-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Iconnect, and thousands of servers like it.
This server
Across the catalogue