get_adsets
AI agents call get_adsets 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 strongly indicates a retrieval operation that queries existing adsets without side effects. Although the description is empty, the naming convention and sibling context (create/delete tools are separate) confirm this is a read-only query operation. Even in an ad management system, retrieving campaign data poses minimal risk compared to creation or deletion operations.
From the tool's definition Tool name is 'get_adsets' which follows the read-operation naming pattern (get/fetch). Sibling tools include create_adset, create_campaign, and delete_campaign_structure, establishing context that this server manages ad campaigns; 'get_adsets' retrieves…
Attacks that exploit this kind of access
get_adsets. 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_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 KonQuest Meta Ads MCP. Nothing to install.
get_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 get_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 get_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.
get_adsets 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 →