Search LinkedIn Geo ID by location (for location-based filtering). Returns cleaned data in TOON format.
AI agents call search_geo_id to retrieve information from LinkedIn MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves location-based geographic identifiers from LinkedIn for filtering purposes. It performs a straightforward query operation with no side effects, data modification, code execution, financial implications, or irreversible actions. The returned data is used as input for other filters rather than as an action itself, confirming Read category classification.
From the tool's definition The tool description explicitly states it 'Search[es] LinkedIn Geo ID by location' and 'Returns cleaned data', indicating data retrieval with no modification, deletion, or execution.
Attacks that exploit this kind of access
Search LinkedIn Geo ID by location (for location-based filtering). Returns cleaned data in TOON format. It is categorised as a Read tool in the LinkedIn MCP Server MCP Server, which means it retrieves data without modifying state.
Register the LinkedIn MCP Server MCP server in PolicyLayer and add a rule for search_geo_id: 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 MCP Server. Nothing to install.
search_geo_id 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 search_geo_id 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 search_geo_id. 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.
search_geo_id is provided by the LinkedIn MCP Server MCP server (jing-yilin/linkedin-mcp-server). 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 →