Skills Microsoft Graph API
📦
Microsoft Graph API
v0.3.0 Content revision r1 High Risk 🌐 Network access⚙️ External commands📁 Filesystem access🔑 Env variables
Connect Microsoft Graph Email and Calendar
Microsoft 365 email and calendar work often requires switching tools and copying data manually. This skill lets an AI assistant use Microsoft Graph scripts for authenticated Outlook mail and calendar tasks.
Supports: Claude Codex Code(CC)
Stop for confirmation before installing.
Review the plan and obtain explicit user consent before changing files.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Agent request
Review the Skillstore skill "Microsoft Graph API" from https://skillstore.io/skills/bltgv-microsoft-graph-api.md and its manifest at https://skillstore.io/api/skills/bltgv-microsoft-graph-api/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "Microsoft Graph API". Show my next five calendar events.
Expected outcome:
A concise list of upcoming events with time, subject, organizer, location, and attendee status when available.
Using "Microsoft Graph API". Search for messages from finance about invoices.
Expected outcome:
A ranked email summary with sender, received date, subject, read status, attachment status, and short preview text.
Using "Microsoft Graph API". Send a reminder email to the team after I approve it.
Expected outcome:
A confirmation summary showing the approved recipients, subject, and sent status.
Security Audit
High Riskv9 • 7/19/2026 Open versioned report
Most static alerts are false positives caused by TypeScript template literals, Markdown backticks, example identifiers, and official Microsoft URLs. Confirmed risks include OAuth network operations, immediate email sending, and plaintext credential storage. Semantic review also found weak secret-file permissions, indirect prompt-injection exposure, and unconfirmed calendar creation.
11
Files scanned
2,369
Lines analyzed
9
Review items
0
False positives ignored
Confirmed security concerns (4)
High
Credential JSON file
const CREDENTIALS_FILE = join(CONFIG_DIR, "credentials.json");
This path is used to persist Microsoft Graph access and refresh tokens as plaintext JSON. Disclosure of the file can grant delegated mailbox and calendar access.
High
OAuth Secret Files Lack Restrictive Permissions
Credential and pending-auth files contain tokens or device codes. The write operations do not set restrictive modes, so other local users may read them.
Both functions write sensitive JSON with writeFile and no mode option. Default permissions depend on umask and can permit local disclosure.
High
Indirect Prompt Injection Exposure
Email bodies and calendar text are returned directly to the agent. Malicious content may influence later email or calendar actions without an untrusted-data boundary.
The scripts return externally controlled message bodies and event fields verbatim. The skill instructions provide no rule to treat retrieved content only as data.
Medium
Calendar Creation Has No Confirmation Gate
The create command posts events and attendee invitations immediately. The skill does not require a final user review of subject, time, or recipients.
The create branch validates required fields and posts immediately. The usage instructions show direct create commands without a confirmation step.
Capability review items (9)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
High
Email sending capability
await graphPost(token, "/me/sendMail", { message });
This call sends a message through the authenticated mailbox immediately. The script has no recipient preview or explicit confirmation gate before the external side effect.
Low
Fetch API call
const response = await fetch(url, {
The fetch sends an OAuth bearer token to Microsoft Graph and accesses mailbox or calendar data. The destination is fixed and legitimate, but the network capability is security-relevant.
Low
Fetch API call
const response = await fetch(url, {
The fetch sends an OAuth bearer token to Microsoft Graph and accesses mailbox or calendar data. The destination is fixed and legitimate, but the network capability is security-relevant.
Low
Fetch API call
const response = await fetch(url, {
The fetch sends an OAuth bearer token to Microsoft Graph and accesses mailbox or calendar data. The destination is fixed and legitimate, but the network capability is security-relevant.
Low
Fetch API call
const response = await fetch(url, {
The fetch sends an OAuth bearer token to Microsoft Graph and accesses mailbox or calendar data. The destination is fixed and legitimate, but the network capability is security-relevant.
Low
Fetch API call
const response = await fetch(url, {
The fetch performs OAuth device-code, token, or refresh exchanges with Microsoft identity endpoints. This is expected, but it transmits authentication material over the network.
Low
Fetch API call
const response = await fetch(url, {
The fetch performs OAuth device-code, token, or refresh exchanges with Microsoft identity endpoints. This is expected, but it transmits authentication material over the network.
Low
Fetch API call
const response = await fetch(url, {
The fetch performs OAuth device-code, token, or refresh exchanges with Microsoft identity endpoints. This is expected, but it transmits authentication material over the network.
Low
Fetch API call
const response = await fetch(`https://graph.microsoft.com/v1.0${endpoint}`, {
The fetch sends an OAuth bearer token to Microsoft Graph and accesses mailbox or calendar data. The destination is fixed and legitimate, but the network capability is security-relevant.
Risk Factors
🌐 Network access (25)
references/graph-api.md:241 scripts/auth.ts:77 scripts/auth.ts:83 scripts/auth.ts:171 scripts/calendar.ts:125 scripts/calendar.ts:143 scripts/calendar.ts:123 scripts/calendar.ts:141 scripts/emails.ts:122 scripts/emails.ts:140 scripts/emails.ts:120 scripts/emails.ts:138 scripts/emails.ts:325 scripts/lib/device-code.ts:45 scripts/lib/device-code.ts:87 scripts/lib/device-code.ts:152 scripts/lib/device-code.ts:38 scripts/lib/device-code.ts:78 scripts/lib/device-code.ts:142 scripts/lib/graph-client.ts:155 scripts/lib/graph-client.ts:62 scripts/lib/graph-client.ts:155 SKILL.md:33 SKILL.md:42 SKILL.md:55
⚙️ External commands (50)
scripts/auth.ts:57-104 scripts/auth.ts:120 scripts/auth.ts:121 scripts/auth.ts:122 scripts/auth.ts:124 scripts/auth.ts:127 scripts/auth.ts:129 scripts/auth.ts:140 scripts/auth.ts:142 scripts/auth.ts:155 scripts/auth.ts:156 scripts/auth.ts:158 scripts/auth.ts:160 scripts/auth.ts:163 scripts/auth.ts:165 scripts/auth.ts:171 scripts/auth.ts:178 scripts/auth.ts:179 scripts/auth.ts:180 scripts/auth.ts:181 scripts/auth.ts:199 scripts/auth.ts:200 scripts/auth.ts:201 scripts/calendar.ts:66-113 scripts/calendar.ts:123 scripts/calendar.ts:127 scripts/calendar.ts:134 scripts/calendar.ts:141 scripts/calendar.ts:146 scripts/calendar.ts:154 scripts/calendar.ts:287 scripts/calendar.ts:305 scripts/calendar.ts:325 scripts/calendar.ts:410 scripts/emails.ts:65-110 scripts/emails.ts:120 scripts/emails.ts:124 scripts/emails.ts:131 scripts/emails.ts:138 scripts/emails.ts:143 scripts/emails.ts:151 scripts/emails.ts:198 scripts/emails.ts:224 scripts/emails.ts:252 scripts/emails.ts:273 scripts/emails.ts:339 scripts/lib/auth-handler.ts:66-79 scripts/lib/auth-handler.ts:79-194 scripts/lib/device-code.ts:38 scripts/lib/device-code.ts:55
📁 Filesystem access (3)
🔑 Env variables (2)
Audited by: codex View Audit History →
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/bltgv-microsoft-graph-api/audits/9?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/bltgv-microsoft-graph-api?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/bltgv-microsoft-graph-api?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/bltgv-microsoft-graph-api/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/bltgv-microsoft-graph-api.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
BLTGV. (2026). Microsoft Graph API security audit report (audit version 9) [Author version 0.3.0]. Skillstore. https://skillstore.io/skills/bltgv-microsoft-graph-api/audits/9BibTeX citation
@techreport{bltgv-bltgv-microsoft-graph-api-2026,
author = {BLTGV},
title = {Microsoft Graph API security audit report (audit version 9)},
institution = {Skillstore},
year = {2026},
number = {9},
url = {https://skillstore.io/skills/bltgv-microsoft-graph-api/audits/9},
note = {Author version 0.3.0}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "Microsoft Graph API security audit report (audit version 9)"
version: "0.3.0"
type: report
authors:
- name: "BLTGV"
date-released: "2026-07-19"
url: "https://skillstore.io/skills/bltgv-microsoft-graph-api/audits/9"
identifiers:
- type: other
value: "skillstore:bltgv-microsoft-graph-api:audit:9"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: Medium 64
Architecture
100
Maintainability
87
Content
71
Community
74
Spec Compliance
What You Can Build
Review Daily Communications
Check unread mail, search important messages, and inspect upcoming meetings from one assistant workflow.
Coordinate Team Meetings
Find calendar availability context, create meeting events, and send follow-up emails through Microsoft 365.
Support Office Automation
Use repeatable scripts to list folders, search mailbox records, and create calendar items for routine requests.
Try These Prompts
List Today's Schedule
Show my Outlook calendar events for today using the Microsoft Graph skill. Include start time, title, organizer, and location.
Search Recent Mail
Search my Outlook email for messages about quarterly planning from the last month. Summarize sender, subject, date, and preview.
Draft And Send Email
Prepare an email to the project team with this update. Show me the recipients, subject, and body for approval before sending.
Create A Meeting Workflow
Find my meetings next week, identify a free one-hour slot, then create a review meeting with the listed attendees after I confirm the details.
Best Practices
- Use named profiles to separate work, personal, and tenant-specific Microsoft accounts.
- Ask for explicit confirmation before sending email or creating calendar events.
- Use the smallest Graph permission scope needed for the current task.
Avoid
- Do not send email or create events from inferred intent alone.
- Do not paste sensitive message bodies into shared prompts or logs.
- Do not reuse a broad default OAuth app when tenant policy requires a dedicated app registration.
Frequently Asked Questions
What Microsoft services does this skill use?
It uses Microsoft Graph for Outlook mail, Outlook calendar, and Microsoft account profile authentication.
How does authentication work?
The scripts use Microsoft device-code authentication and store refreshed credentials for later commands.
Can it send email?
Yes. It can send email after authentication with Mail.Send permission and user approval.
Can it create calendar events?
Yes. It can create events with subject, start time, end time, location, description, attendees, and all-day settings.
Where are credentials stored?
Credentials are stored locally in a JSON file under ~/.config/api-skills in the user home directory.
Does it handle attachments?
No. The current scripts expose message metadata, body content, folders, email sending, and calendar operations.