Secure Calendar CLI Unified Protection
Your organization uses Google Calendar, Outlook Calendar, or both. The Secure Calendar CLI applies one set of rules across all calendar providers, so AI agents get consistent, controlled access regardless of the platform.
The Problem
Giving AI agents direct access to your data is risky. Here's what can go wrong.
Separate Calendar Security Configurations
Google Calendar and Outlook Calendar have different APIs, permission scopes, and admin tools, requiring two independent security setups that inevitably diverge.
Inconsistent Data Exposure Across Providers
Without a normalization layer, an AI agent might see attendee emails from one provider but not the other, creating an inconsistent security posture.
No Cross-Provider Calendar Governance
There is no built-in way to enforce a rule like 'AI agents should never see meeting attendees' across both Google Calendar and Outlook Calendar.
How PortEden Protects You
Six layers of security between AI agents and your data.
Single Config for All Calendars
Write your calendar security rules once and the CLI enforces them identically on Google Calendar and Outlook Calendar.
Normalized Event Data
The CLI normalizes calendar event data from both providers into a consistent format before applying your visibility rules.
Cross-Platform Attendee Controls
Block AI agents from seeing specific attendees across both calendar providers with a single rule definition.
Calendar-Specific Access Scoping
Restrict agents to specific calendars within each provider, keeping personal, team, and HR calendars hidden.
Get Started in 3 Steps
Install and Connect Calendars
Install the PortEden CLI and connect your Google Calendar and Outlook Calendar via their respective OAuth flows.
Define Calendar Policies
Create your config file with visibility rules, attendee controls, and calendar scoping that applies to both providers.
Deploy and Monitor
Route AI agents through PortEden so calendar queries to any provider are filtered through your rules with unified audit logging.
Without vs. With PortEden
Without PortEden
- Separate security configurations for Google Calendar and Outlook Calendar
- Different APIs return different event formats with different levels of detail
- Attendee visibility rules maintained separately per provider
- Calendar audit logs split between Google Workspace and Microsoft 365
With PortEden
- One config file governs calendar access across both providers
- Normalized event format ensures consistent data filtering
- Attendee rules apply identically across Google and Outlook Calendar
- Single audit log captures all calendar access from all agents