Compare LinkedIn campaign performance across two time periods. wow (week-over-week): last 7d vs prior 7d. mom (month-over-month): last 30d vs prior 30d. yoy (year-over-year): last 30d vs same 30d last year. Returns per-entity rows (keyed by campaign/creative URN) with _current, _prior, _delta, an...
Bulk/mass operation — affects multiple targets
Part of the LinkedIn Campaign Manager MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call li_compare_periods to retrieve information from LinkedIn Campaign Manager without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though li_compare_periods only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
tools:
li_compare_periods:
rules:
- action: allowSee the full LinkedIn Campaign Manager policy for all 19 tools.
Agents calling read-class tools like li_compare_periods have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.
Compare LinkedIn campaign performance across two time periods. wow (week-over-week): last 7d vs prior 7d. mom (month-over-month): last 30d vs prior 30d. yoy (year-over-year): last 30d vs same 30d last year. Returns per-entity rows (keyed by campaign/creative URN) with _current, _prior, _delta, and _pct_change columns for every requested metric. Deltas are computed server-side so you do not need to post-process. Useful for weekly/monthly performance reports and anomaly detection.. It is categorised as a Read tool in the LinkedIn Campaign Manager MCP Server, which means it retrieves data without modifying state.
Add a rule in your Intercept YAML policy under the tools section for li_compare_periods. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the LinkedIn Campaign Manager MCP server.
li_compare_periods 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 li_compare_periods rule in your Intercept 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 Intercept policy for li_compare_periods. 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.
li_compare_periods is provided by the LinkedIn Campaign Manager MCP server (linkedin-campaign-manager-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.