get_campaigns
AI agents call get_campaigns to retrieve information from KonQuest Meta Ads MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'get_' prefix is a standard convention for read-only retrieval operations that query and return data without side effects. While the description is uninformative, the tool name itself and the prevalence of 'get' methods for read operations in the sibling tools (which include create, delete, check, and diagnose operations) support classification as a Read operation with no destructive or execute capabilities.
From the tool's definition Tool name 'get_campaigns' indicates a retrieval operation. The empty description limits direct confirmation, but the name pattern and context within a campaign management system strongly suggests querying/listing existing campaign data rather than modifying…
Attacks that exploit this kind of access
get_campaigns. It is categorised as a Read tool in the KonQuest Meta Ads MCP MCP Server, which means it retrieves data without modifying state.
Register the KonQuest Meta Ads MCP server in PolicyLayer and add a rule for get_campaigns: 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 KonQuest Meta Ads MCP. Nothing to install.
get_campaigns 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 get_campaigns 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 get_campaigns. 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.
get_campaigns is provided by the KonQuest Meta Ads MCP server (brandu-mos/konquest-meta-ads-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →