metaAds_list_adsets
List ad sets for an ad account
This record as markdown: /tools/io-github-alifanov-scopegate/metaads-list-adsets.md
What metaAds_list_adsets does on ScopeGate
AI agents call metaAds_list_adsets to retrieve information from ScopeGate without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why metaAds_list_adsets is rated Low
This tool retrieves and queries data about ad sets from a Meta Ads account without creating, modifying, deleting, or executing any operations. It produces no side effects and falls squarely into the Read category.
From the tool's definition Tool name 'metaAds_list_adsets' and description 'List ad sets for an ad account' indicate a retrieval/query operation with no side effects. The verb 'list' is a read-only operation that retrieves existing data about ad sets.
Attacks that exploit this kind of access
The rule that runs metaAds_list_adsets safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ScopeGate, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For metaAds_list_adsets, this is the rule to start with:
metaAds_list_adsets 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 ScopeGate, apply this rule, and every metaAds_list_adsets call is checked against it from then on.
Questions about metaAds_list_adsets
List ad sets for an ad account. It is categorised as a Read tool in the ScopeGate MCP Server, which means it retrieves data without modifying state.
Register the ScopeGate MCP server in PolicyLayer and add a rule for metaAds_list_adsets: 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 ScopeGate. Nothing to install.
metaAds_list_adsets 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 metaAds_list_adsets 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 metaAds_list_adsets. 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.
metaAds_list_adsets is provided by the ScopeGate MCP server (https://mcp.scopegate.cloud/{api_key}). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ScopeGate, and thousands of servers like it.
This server
Across the catalogue