Tests CAPI setup by sending a test event that won
AI agents invoke meta_test_conversion_events to trigger actions in Meta MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
The tool sends a test event to Meta's Conversions API (CAPI), which is an external operation that triggers side effects on Meta's systems. While labeled as a 'test', it still executes an actual API call and sends data externally. The description appears truncated ('that won' is incomplete), lowering confidence slightly.
From the tool's definition 'Tests CAPI setup by sending a test event' — triggers an external operation (sending a test conversion event to Meta's Conversions API)
Documented attack patterns abuse exactly the kind of access meta_test_conversion_events 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_test_conversion_events:
{
"version": "1",
"default": "deny",
"tools": {
"meta_test_conversion_events": {
"limits": [
{
"counter": "meta_test_conversion_events_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} meta_test_conversion_events stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Tests CAPI setup by sending a test event that won. It is categorised as a Execute tool in the Meta MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Meta MCP Server MCP server in PolicyLayer and add a rule for meta_test_conversion_events: 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_test_conversion_events is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the meta_test_conversion_events 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_test_conversion_events. 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_test_conversion_events 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.