Fetch full LinkedIn personal profile data for a given URL.
AI agents call get_personal_profile to retrieve information from Social Media Scraper - Custom 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 personal LinkedIn profile information without side effects—a read operation. However, severity is high because fetching full personal profile data at scale raises privacy and data protection concerns (potential GDPR/CCPA violations, unauthorized collection of PII), even though the tool itself is not destructive or financially harmful.
From the tool's definition Tool name 'get_personal_profile' and description 'Fetch full LinkedIn personal profile data' indicate data retrieval with no modification. The verb 'fetch' and lack of any write/delete/execute language confirm read-only operation.
Documented attack patterns abuse exactly the kind of access get_personal_profile gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Social Media Scraper - Custom MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_personal_profile:
{
"version": "1",
"default": "deny",
"tools": {
"get_personal_profile": {}
}
}get_personal_profile 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.
Fetch full LinkedIn personal profile data for a given URL. It is categorised as a Read tool in the Social Media Scraper - Custom MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Social Media Scraper - Custom MCP Server MCP server in PolicyLayer and add a rule for get_personal_profile: 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 Social Media Scraper - Custom MCP Server. Nothing to install.
get_personal_profile 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 get_personal_profile 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 get_personal_profile. 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.
get_personal_profile is provided by the Social Media Scraper - Custom MCP Server MCP server (sharan-kumar-r/custom-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 5 Social Media Scraper - Custom MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
5 Social Media Scraper - Custom MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.