Make MCP audit logs: check plan access and read-only scope

October 15, 2026

Before using Make MCP to investigate audit events, separate tool availability, access to the underlying data and the permissions of the complete connection. Official descriptions currently leave a plan-access question unresolved. This guide can help you prepare a verification request, but it does not promise Free access to Enterprise audit data or recommend a purchase to resolve the uncertainty.

Two official descriptions need reconciliation

The October 6 official staff spotlight described MCP tools for listing, filtering and viewing audit events. The October 9 roundup says the audit tools are available on all plans. However, the detailed audit-log help and staff explanation describe underlying audit logs as Enterprise. LessWork Lab has not tested the accounts or obtained a formal clarification that reconciles these statements.Sources: Review audit logs with MCP · October 9 Make roundup · Make audit logs

The audit-query tools are described as read-only. Make MCP as a whole can also expose scenario-running and management or modification tools, depending on scopes. The developer documentation distinguishes scenario-run access from paid management tools. A read-only audit tool does not make an entire connection read-only; review the selected permissions and actual tools rather than inferring access from the integration name.Sources: Make MCP Server · Review audit logs with MCP

Ask what evidence you need

Audit events, scenario execution logs and platform event notifications answer different questions. Start with the incident: which change are you tracing, in which organization or team, and under which administrator role? The audit help describes organization/team administrator conditions and 12-month storage, but that does not prove access in your plan or complete evidence for a particular incident.Sources: Make audit logs

For a hypothetical investigation of an unexpected workflow change, define the relevant organization and period before asking an AI client to search. A returned tool name is not evidence that it can retrieve the required records. An empty result cannot, without access and filter checks, establish that nobody made a change. This example is a preparation method, not a tested audit investigation.

A permission and availability checklist

  1. Record the audit question, organization, team and responsible administrator. Identify which evidence belongs to audit logs and which requires execution records or notifications. Avoid merging them into a single guarantee of complete incident visibility.
  2. Within an already authorized account context, verify visible tools, current plan and actual event data. Record missing or denied access as unresolved. Do not use an ordinary community user's general comment to override detailed official plan conditions.
  3. Grant only the reading permissions needed for the task and review run or management tools separately. Inspect the client and connection scope together. LessWork Lab did not create an MCP connection, expand permissions or retrieve private audit records for this guide.
  4. Retain the official conflict in your decision record. Seek written brand clarification or evidence from a genuinely authorized account before lifting the access claim hold. Until then, do not promise Free Enterprise audit data or recommend upgrading solely on the roundup sentence.

Do not convert a tool announcement into a quote

Enterprise is listed with custom pricing; no quote was obtained. An optional AI or MCP client's subscription and usage costs are also unverified. We did not subscribe or spend money. A listed tool cannot establish that the data behind it is free, and an unknown amount should remain unknown rather than being recorded as zero.Sources: Make pricing

No newly negotiated reader coupon or verified calendar deadline is available here. “All plans” is an availability statement under review, not a confirmed free-data offer. Country-specific checkout, currency, taxes, renewal and promotion eligibility were not verified. Keep purchasing claims and an access-promising CTA disabled while the underlying entitlement is unresolved.

Two questions to resolve before use

Can a Free account read all audit logs? The two official descriptions do not establish that. Tool listing and underlying Enterprise data entitlement may be different, but their exact relationship was not verified. This guide preserves that uncertainty rather than choosing the more generous statement.Sources: October 9 Make roundup · Make audit logs

Is the entire MCP connection read-only? Only the audit-query tools are described that way. Other tools can run or manage scenarios according to scopes. Confirm the actual selected permissions before connecting; the name of an integration is not a substitute for reviewing its abilities.Sources: Make MCP Server

Official material reviewed October 9, 2026; no product test, complete incident proof, measured saving or ROI. Make's public affiliate terms describe 35% of eligible subscription payments for 12 months from referred registration, excluding extra credits. October 4 local account/link/setup records do not verify current media approval, qualifying transactions, payable commission or Taiwan bank receipt. This informational candidate retains the purchase-claim hold and has no affiliate CTA.Sources: Make Affiliate program

Official sources

Reviewed:

Related reading