Sends an offline conversion event to a Meta offline event set. Used for tracking in-store purchases, phone orders, or other offline conversions. Args: - event_set_id (string): Offline event set ID (from meta_list_offline_event_sets) - event_name (string): Event name (e.g.,
AI agents use meta_send_offline_event to create or update resources in Meta MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Meta MCP Server environment.
This tool writes data (offline conversion events) to Meta's analytics/tracking system. It creates new event records that will be stored and used for conversion tracking and campaign optimization. While it modifies data, it is reversible (events can be corrected or removed), so it does not rise to Destructive.
From the tool's definition Tool sends/submits an offline conversion event to Meta's offline event set, modifying the event tracking data. Description states it 'Sends an offline conversion event,' which is a create/write operation that adds data to Meta's system.
Documented attack patterns abuse exactly the kind of access meta_send_offline_event gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Meta MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for meta_send_offline_event:
{
"version": "1",
"default": "deny",
"tools": {
"meta_send_offline_event": {
"limits": [
{
"counter": "meta_send_offline_event_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}meta_send_offline_event stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Sends an offline conversion event to a Meta offline event set. Used for tracking in-store purchases, phone orders, or other offline conversions. Args: - event_set_id (string): Offline event set ID (from meta_list_offline_event_sets) - event_name (string): Event name (e.g.,. It is categorised as a Write tool in the Meta MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Meta MCP Server MCP server in PolicyLayer and add a rule for meta_send_offline_event: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Meta MCP Server. Nothing to install.
meta_send_offline_event is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the meta_send_offline_event rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for meta_send_offline_event. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
meta_send_offline_event is provided by the Meta MCP Server MCP server (oliverames/meta-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Meta MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
200 Meta MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.