metaAds_get_campaign
Get details of a campaign
This record as markdown: /tools/io-github-alifanov-scopegate/metaads-get-campaign.md
What metaAds_get_campaign does on ScopeGate
AI agents call metaAds_get_campaign 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_get_campaign is rated Low
This tool retrieves campaign details from Meta Ads, which is a read-only query operation with no side effects. It does not create, modify, delete, execute code, or commit financial transactions. The blast radius of misuse is minimal—an agent could view campaign data it shouldn't access, but cannot alter campaigns or incur costs.
From the tool's definition Tool name 'metaAds_get_campaign' and description 'Get details of a campaign' indicate retrieval of campaign information without modification.
Attacks that exploit this kind of access
The rule that runs metaAds_get_campaign 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_get_campaign, this is the rule to start with:
metaAds_get_campaign 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_get_campaign call is checked against it from then on.
Questions about metaAds_get_campaign
Get details of a campaign. 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_get_campaign: 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_get_campaign 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_get_campaign 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_get_campaign. 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_get_campaign 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