meta_ads_split_tests_end
Ends a running Split Test immediately, before its scheduled
This record as markdown: /tools/logly-mureo/meta-ads-split-tests-end.md
What meta_ads_split_tests_end does on Mureo
AI agents call meta_ads_split_tests_end to permanently remove resources in Mureo, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why meta_ads_split_tests_end is rated Critical
This tool forcibly terminates a running split test before its scheduled completion. This is an irreversible action — once ended, the test cannot be resumed and any in-progress experimental data is permanently lost. The premature termination cannot be undone, making this a Destructive operation.
From the tool's definition Ends a running Split Test immediately, before its scheduled
Attacks that exploit this kind of access
The rule that runs meta_ads_split_tests_end safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mureo, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For meta_ads_split_tests_end, this is the rule to start with:
meta_ads_split_tests_end is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Mureo, apply this rule, and every meta_ads_split_tests_end call is checked against it from then on.
Questions about meta_ads_split_tests_end
Ends a running Split Test immediately, before its scheduled. It is categorised as a Destructive tool in the Mureo MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Mureo MCP server in PolicyLayer and add a rule for meta_ads_split_tests_end: 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 Mureo. Nothing to install.
meta_ads_split_tests_end is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the meta_ads_split_tests_end 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_ads_split_tests_end. 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_ads_split_tests_end is provided by the Mureo MCP server (logly/mureo). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mureo, and thousands of servers like it.
Across the catalogue