Agent Upstart

Cool things people are building with agents — and practical help getting the most out of them.

Playbooks · Coding tasks

Apify MCP Server 0.21.8 hardens the bridge

Written November 13, 2026

The 0.21.8 release marks destructive operations, stops failure logs keeping request details, and bounds log reading. A safety patch, read closely.

What changed

Apify shipped version 0.21.8 of its MCP server on November 13. The release notes list nine bug fixes and nothing else — no new tools, no new surface. Read as a group, the fixes tighten three things an operator cares about: which operations carry a destructive label, what the server writes into logs, and how much data a single read can pull back.

Anyone who runs this server hands an agent a path into an Apify account: Actors, datasets, saved tasks, and schedules that run work on their own. Small fixes to labels and logs change what a careful host will ask about before it acts, and what is left sitting in a log file afterwards.

Two operations are now labelled destructive

The headline fix marks update-schedule and update-actor-task as destructive. A schedule decides when Actors run without anyone present. An Actor task holds the saved configuration a run starts from. Changing either one changes future behaviour on the account, which is why the label fits.

MCP tool annotations are how a server tells a host how risky a call is. Hosts that honour the destructive hint can stop and ask before the call goes through, or refuse it under a strict policy. Before 0.21.8, a host treating these two updates as routine writes would wave them past. Now the server itself supplies the warning, and a host that ignores it is making its own choice.

Logs hold less, and reads are bounded

The rest of the list

Three fixes harden how the server handles untrusted shapes. It validates resource identifiers and request paths before making API calls. It normalizes IDs in linear time and limits ID and name length, which closes off a class of slow, oversized inputs. It also finds string literals and detects email patterns in linear time, and treats object property names as ordinary selectors and keys. The last change swaps the @apify/datastructures dependency for a Map-based LRU cache — one line in the notes, and the only pure performance item in the release.

How to get it

The project README gives two routes. The hosted server at mcp.apify.com always runs the latest version, so hosted users get 0.21.8 without doing anything. The local stdio build runs the npm version you install, through npx -y @apify/actors-mcp-server; local users take the fix when they move to the new package version. If your host asks before destructive calls, the two relabelled tools are the reason an update prompt may appear where none did last week.

One habit is worth adopting with this release: pin the tool set you actually use. The README notes that everything beyond the default categories is opt-in by category or by tool name. A narrower tool set plus the new destructive labels gives a host two separate chances to stop a call you never meant to allow.

Related playbooks

Sources

Back to: Coding playbooks hub · Also: Patch your MCP reference servers now