Meta MCP lets AI agents create apps — use cases can't be undone

Meta's Social Technologies MCP server can now do the part of Meta app setup that used to eat an afternoon. On October 26, Meta announced six new tools that let your coding agent create a Meta app, find or create a Business Portfolio, link the two, and add a use case like WhatsApp Business messaging. Four of those six tools write to your account. One of them writes something the server cannot take back.

What actually happened

The server launched in June as a mostly read-only helper for API discovery, troubleshooting and webhook debugging. The new tools move it into the app lifecycle. Per Meta's MCP documentation:

• devtools_app_create makes an app in development mode and returns an app ID — not the app secret
• devtools_business_list and devtools_business_create find or make a Business Portfolio (creating one needs the optional business_management permission)
• devtools_app_business_manage links an app to a portfolio, and refuses apps another portfolio already owns
• devtools_app_use_cases and devtools_app_use_cases_manage list and add use cases

The agent asks you to confirm before each write. App and portfolio creation carry per-user safety limits, and Meta warns that failed validation or a declined or timed-out confirmation can count as an attempt. Secrets stay in the App Dashboard behind re-authentication; Meta says they "will not be shared via an agent conversation."

The catch is in the docs: adding a use case grants its privileges, and the server cannot remove it later. Rollout is gradual. The blog says the tools may not be on every account yet, and if you already have the server connected, you need to reconnect to see them.

Why it matters for your business

A confirmation prompt is a control only if the person clicking "yes" knows what they're approving. When an agent says "I'll add WhatsApp Business messaging to your app," that sounds like a settings toggle. It is a permanent grant of messaging privileges on an app tied to your business identity.

So treat the write tools the way you'd treat a production database migration. Decide the use cases before the session, not during it. Run the agent against a dedicated development portfolio first. Don't grant business_management unless you actually need the agent to create portfolios. And keep a short log of which apps and use cases an agent created, because six months from now nobody will remember why that app exists.

We like this release. Meta kept secrets out of the chat and put limits on creation. The rest of the guardrail is on you.

Sources: Meta for Developers blog, Social Technologies MCP docs.