meta_ads_split_tests_get
Fetches the full detail record for a single Split Test
This record as markdown: /tools/logly-mureo/meta-ads-split-tests-get.md
What meta_ads_split_tests_get does on Mureo
AI agents call meta_ads_split_tests_get to retrieve information from Mureo without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why meta_ads_split_tests_get is rated Low
This tool retrieves read-only information about an existing Meta Ads split test. Fetching details poses minimal risk: it returns data already created and does not modify state, trigger actions, or commit financial transactions. The blast radius if misused by an agent is limited to potential unauthorized disclosure of campaign analytics metadata.
From the tool's definition Tool name contains 'get' and description states 'Fetches the full detail record for a single Split Test' — purely a retrieval operation with no modification, deletion, or execution of external operations.
Attacks that exploit this kind of access
The rule that runs meta_ads_split_tests_get 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_get, this is the rule to start with:
meta_ads_split_tests_get is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Mureo, apply this rule, and every meta_ads_split_tests_get call is checked against it from then on.
Questions about meta_ads_split_tests_get
Fetches the full detail record for a single Split Test. It is categorised as a Read tool in the Mureo MCP Server, which means it retrieves data without modifying state.
Register the Mureo MCP server in PolicyLayer and add a rule for meta_ads_split_tests_get: 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_get is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the meta_ads_split_tests_get 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_get. 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_get 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.
This server
Across the catalogue