AI agents call linkedin.campaigns.list to retrieve information from Ads without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only queries and returns information about existing LinkedIn ad campaigns. It has no side effects, does not modify any data, and poses minimal risk even if called repeatedly or with unexpected parameters. The blast radius is limited to information disclosure of campaign metadata that the caller likely already has authorization to view.
From the tool's definition Tool name contains 'list' and description states 'List LinkedIn ad campaigns with status, budget, and optional per-campaign analytics' — purely retrieves campaign data without creating, modifying, deleting, or executing operations.
Attacks that exploit this kind of access
List LinkedIn ad campaigns with status, budget, and optional per-campaign analytics. It is categorised as a Read tool in the Ads MCP Server, which means it retrieves data without modifying state.
Register the Ads MCP server in PolicyLayer and add a rule for linkedin.campaigns.list: 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 Ads. Nothing to install.
linkedin.campaigns.list 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 linkedin.campaigns.list 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 linkedin.campaigns.list. 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.
linkedin.campaigns.list is provided by the Ads MCP server (manlikemuneeb/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 →