twitterAds_get_campaign_stats
Get campaign performance statistics
This record as markdown: /tools/io-github-alifanov-scopegate/twitterads-get-campaign-stats.md
What twitterAds_get_campaign_stats does on ScopeGate
AI agents call twitterAds_get_campaign_stats 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 twitterAds_get_campaign_stats is rated Low
This tool retrieves performance metrics from Twitter Ads campaigns—a query operation with no side effects. No data is created, modified, deleted, or financial obligations incurred. The risk is low since an agent simply reading campaign statistics cannot cause material harm, though access should still be scoped per the ScopeGate server's purpose.
From the tool's definition Tool name 'get_campaign_stats' and description 'Get campaign performance statistics' indicate retrieval of existing data with no modification, deletion, or financial action. The 'get' verb and 'statistics' (read-only metrics) confirm a read operation.
Attacks that exploit this kind of access
The rule that runs twitterAds_get_campaign_stats 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 twitterAds_get_campaign_stats, this is the rule to start with:
twitterAds_get_campaign_stats 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 twitterAds_get_campaign_stats call is checked against it from then on.
Questions about twitterAds_get_campaign_stats
Get campaign performance statistics. 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 twitterAds_get_campaign_stats: 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.
twitterAds_get_campaign_stats 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 twitterAds_get_campaign_stats 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 twitterAds_get_campaign_stats. 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.
twitterAds_get_campaign_stats 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