AI agents call linkedin_ads_get_targeting_facets to retrieve information from Linkedin without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves metadata about available targeting facets for LinkedIn ads - essentially querying a list of targeting parameters. It has no side effects, does not create or modify data, does not execute operations, and does not involve financial transactions. It is a straightforward read operation with minimal risk if misused by an AI agent.
From the tool's definition Tool name includes 'get_' prefix and description states 'Get available targeting options', indicating data retrieval with no modification or execution of external operations.
Attacks that exploit this kind of access
Get available targeting options. It is categorised as a Read tool in the Linkedin MCP Server, which means it retrieves data without modifying state.
Register the Linkedin MCP server in PolicyLayer and add a rule for linkedin_ads_get_targeting_facets: 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 Linkedin. Nothing to install.
linkedin_ads_get_targeting_facets 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_ads_get_targeting_facets 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_ads_get_targeting_facets. 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_ads_get_targeting_facets is provided by the Linkedin MCP server (maheidem/linkedin-optimizer-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 →