// SCAN REPORT

AIOS Co-Founder MCP

22 tools. 10 can modify or destroy data without limits.

1 destructive tool with no built-in limits. Policy required.

Last updated: 4 Jul 2026

10 can modify or destroy data

12 read-only

22 tools total

Community server · catalogue entry verified 04/07/2026

How to control AIOS Co-Founder MCP ↓

TOOL MAP

What AIOS Co-Founder MCP exposes to your agents

Read (12) Write / Execute (9) Destructive / Financial (1)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous AIOS Co-Founder MCP tools

Destructive · High calendar_cancel_event Canceling a calendar event removes or modifies an existing commitment irreversibly. Execute · Medium auth_google_start This tool executes an external operation (Google OAuth initialization) rather than simply reading or writing data directly. Execute · High approval_resolve This tool controls the approval gating mechanism described in the server description for 'sensitive operations.' Resolving an approval can trigger any downstream action (e.g., sending emails, modifying calendar events, u Write · Medium approval_request This tool creates (Write category) a new approval record, which is a reversible operation.

10 of AIOS Co-Founder MCP's 22 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control AIOS Co-Founder MCP

PolicyLayer is an MCP gateway — it sits between your AI agents and AIOS Co-Founder MCP, and nothing reaches the server without passing your rules. These are the rules we recommend:

Deny destructive operations

{
  "calendar_cancel_event": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations

{
  "approval_request": {
    "limits": [
      {
        "counter": "approval_request_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "auth_status": {
    "limits": [
      {
        "counter": "auth_status_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register AIOS Co-Founder MCP — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON AIOS CO-FOUNDER →

Instant setup, no code required.

FULL CATALOGUE

All 22 AIOS Co-Founder MCP tools

DESTRUCTIVE 1 tools

Destructive calendar_cancel_event Cancel an event (requires approval).

EXECUTE 2 tools

Execute approval_resolve Approve or deny an action. Execute auth_google_start Start Google OAuth flow and return an authorization URL.

WRITE 7 tools

Write approval_request Create a pending approval record. Write calendar_create_event Create a calendar event (requires approval). Write calendar_update_event Update event details (requires approval). Write compose_email_reply Generate an email reply draft (never sends). Write contacts_create_or_update Create or update a contact (requires approval). Write gmail_apply_labels Apply labels to one or more messages. Write gmail_create_draft Create an email draft only.

READ 12 tools

Read auth_status Return OAuth status for an approval_id or current connection status. Read calendar_find_free_slots Find available time slots in a range. Read calendar_list_events List calendar events in a time range. Read contacts_get Return full contact details. Read contacts_search Search Google Contacts. Read gmail_get_message Return full email content (plain text preferred). Read gmail_get_thread Return all messages in a thread. Read gmail_search Search Gmail messages and return metadata. Read meeting_brief Prepare a meeting brief. Read summarize_email Summarize an email and store assistant memory. Read web_fetch Fetch page content and extract readable text. Read web_search Perform a web search and return top results.

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about AIOS Co-Founder MCP

Can an AI agent delete data through the AIOS Co-Founder MCP server? +

Yes. The AIOS Co-Founder MCP server exposes 1 destructive tools including calendar_cancel_event. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through AIOS Co-Founder MCP? +

The AIOS Co-Founder MCP server has 7 write tools including approval_request, calendar_create_event, calendar_update_event. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach AIOS Co-Founder MCP.

How many tools does the AIOS Co-Founder MCP server expose? +

22 tools across 4 categories: Destructive, Execute, Read, Write. 12 are read-only. 10 can modify, create, or delete data.

How do I enforce a policy on AIOS Co-Founder MCP? +

Register the AIOS Co-Founder MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every AIOS Co-Founder MCP tool call.

Deterministic rules across all 22 AIOS Co-Founder MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON AIOS CO-FOUNDER →

Instant setup, no code required.

22 AIOS Co-Founder MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.