Search through the LinkedIn export data for specific information
AI agents call search_linkedin_data to retrieve information from Mcp Me without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries/retrieves information from LinkedIn export data without creating, modifying, or deleting anything. It is a pure read operation that has no side effects on the underlying data or external systems. The context of the mcp-me server (digital identity layer providing profile data to AI tools) further supports that this is an informational retrieval tool.
From the tool's definition Tool name is 'search_linkedin_data' and description states 'Search through the LinkedIn export data for specific information'—both indicate data retrieval without modification.
Documented attack patterns abuse exactly the kind of access search_linkedin_data gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Me, and nothing reaches the server without passing your rules. This is the rule we recommend for search_linkedin_data:
{
"version": "1",
"default": "deny",
"tools": {
"search_linkedin_data": {}
}
} search_linkedin_data is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Search through the LinkedIn export data for specific information. It is categorised as a Read tool in the Mcp Me MCP Server, which means it retrieves data without modifying state.
Register the Mcp Me MCP server in PolicyLayer and add a rule for search_linkedin_data: 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 Mcp Me. Nothing to install.
search_linkedin_data 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_linkedin_data 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_linkedin_data. 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_linkedin_data is provided by the Mcp Me MCP server (paladini/mcp-me). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mcp Me, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
17 Mcp Me tools catalogued and risk-classified — across an index of 43,000+ MCP servers.