linkedin_search_filters
Get LinkedIn search filter parameter IDs. LinkedIn uses internal IDs instead of text for search filters (location, industry, etc.). Call this before linkedin.search to resolve filter keywords to their LinkedIn parameter IDs.
This record as markdown: /tools/io-github-saloprj-dialogbrain/linkedin-search-filters.md
What linkedin_search_filters does on Dialogbrain
AI agents call linkedin_search_filters to retrieve information from Dialogbrain without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
type | string | Yes | Filter category to resolve (e.g. LOCATION, INDUSTRY, SKILL) |
limit | integer | — | Max results per filter category |
keywords | string | Yes | Keywords to resolve to parameter IDs (e.g. 'Thailand' for LOCATION) |
Parameters from the server's own tool schema.
Why linkedin_search_filters is rated Low
This tool retrieves metadata about LinkedIn's search filter parameters—it queries and returns lookup data without modifying, executing code, or causing side effects. It enables search functionality but does not itself perform searches or execute actions. The function is purely informational/Read category with low severity since it only exposes parameter mappings.
From the tool's definition Tool description states it 'Get[s] LinkedIn search filter parameter IDs' and is used to 'resolve filter keywords to their LinkedIn parameter IDs' before search operations.
Attacks that exploit this kind of access
The rule that runs linkedin_search_filters safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Dialogbrain, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For linkedin_search_filters, this is the rule to start with:
linkedin_search_filters is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Dialogbrain, apply this rule, and every linkedin_search_filters call is checked against it from then on.
Questions about linkedin_search_filters
Get LinkedIn search filter parameter IDs. LinkedIn uses internal IDs instead of text for search filters (location, industry, etc.). Call this before linkedin.search to resolve filter keywords to their LinkedIn parameter IDs. It is categorised as a Read tool in the Dialogbrain MCP Server, which means it retrieves data without modifying state.
linkedin_search_filters accepts 3 parameters: type, limit, keywords. Required: type, keywords. The full parameter table on this page comes from the server's own tool schema.
Register the Dialogbrain MCP server in PolicyLayer and add a rule for linkedin_search_filters: 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 Dialogbrain. Nothing to install.
linkedin_search_filters 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_search_filters 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_search_filters. 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_search_filters is provided by the Dialogbrain MCP server (https://api.dialogbrain.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Dialogbrain, and thousands of servers like it.
This server
Across the catalogue