Secure Outlook Calendar CLI for AI Agents
Microsoft Graph's Calendars.ReadWrite permission exposes every calendar, every event, and every attendee in your Microsoft 365 tenant. The Secure Outlook Calendar CLI puts precise, scriptable boundaries on what AI agents can access.
The Problem
Giving AI agents direct access to your data is risky. Here's what can go wrong.
Calendars.ReadWrite Is All-or-Nothing
Microsoft Graph's calendar permissions grant access to every calendar in a user's account with no native way to scope it down per agent.
Rich Event Metadata Fully Exposed
Outlook Calendar events include attendee lists, meeting body content, Teams links, room bookings, and response statuses, all ingested by agents by default.
Azure AD Calendar Policies Are Not Scriptable
Restricting calendar access in Azure AD requires navigating the portal manually, with no way to test rules in CI or roll them back via git.
How PortEden Protects You
Six layers of security between AI agents and your data.
Graph API Calendar Scoping
Restrict which Outlook calendars each AI agent can access, with the CLI filtering Graph API responses to include only explicitly allowed calendars.
Attendee Redaction
Strip attendee names, emails, and response statuses from calendar event responses before they reach the agent.
Meeting Body Filtering
Control whether agents see the full meeting body, a stripped-text version, or no body at all.
Read-Only Calendar Enforcement
Enforce read-only access for agents even when the underlying Graph API token has Calendars.ReadWrite permissions.
Get Started in 3 Steps
Install and Connect
Install the PortEden CLI with npm and authenticate with your Microsoft 365 account via OAuth.
Configure Calendar Rules
Define which calendars agents can access, what event fields they see, and what time range they can query.
Route and Audit
Point your AI agents to the PortEden proxy so every Graph API calendar call is filtered through your config with full audit logging.
Without vs. With PortEden
Without PortEden
- Calendars.ReadWrite exposes every calendar and event in the tenant
- Attendee lists with email addresses visible to any agent with calendar access
- Meeting bodies with agendas and internal links fully exposed
- Azure AD calendar policies require manual portal configuration
With PortEden
- Per-calendar access controls limit agents to allowed calendars only
- Attendee information stripped from event responses before agents see them
- Meeting body filtering removes sensitive content automatically
- Calendar rules defined in code and deployed via CI/CD pipelines