scrape_linkedin_posts

Scrape recent posts from a LinkedIn profile with engagement metrics. Detect buying signals in their content.

Server GOD MODE INTEL MCP Server johnrippy1980/god-mode-intel-mcp-server
Category Read
Risk class Low
Parameters 00 required

What scrape_linkedin_posts does on GOD MODE INTEL MCP Server

AI agents call scrape_linkedin_posts to retrieve information from GOD MODE INTEL MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why scrape_linkedin_posts needs a policy

This tool retrieves and analyzes publicly available or accessible LinkedIn data. While scraping raises terms-of-service and privacy concerns, the functional operation is fundamentally a read operation—it queries and extracts information without modifying, deleting, or executing code. The 'detect buying signals' component is analysis of retrieved data, not an action with external effects.

From the tool's definition Tool name 'scrape_linkedin_posts' and description 'Scrape recent posts from a LinkedIn profile with engagement metrics. Detect buying signals in their content.' indicate data retrieval with no modification or deletion of data.

Questions about scrape_linkedin_posts

What does the scrape_linkedin_posts tool do? +

Scrape recent posts from a LinkedIn profile with engagement metrics. Detect buying signals in their content. It is categorised as a Read tool in the GOD MODE INTEL MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on scrape_linkedin_posts? +

Register the GOD MODE INTEL MCP Server MCP server in PolicyLayer and add a rule for scrape_linkedin_posts: 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 GOD MODE INTEL MCP Server. Nothing to install.

What risk level is scrape_linkedin_posts? +

scrape_linkedin_posts is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit scrape_linkedin_posts? +

Yes. Add a rate_limit block to the scrape_linkedin_posts 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.

How do I block scrape_linkedin_posts completely? +

Set action: deny in the PolicyLayer policy for scrape_linkedin_posts. 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.

What MCP server provides scrape_linkedin_posts? +

scrape_linkedin_posts is provided by the GOD MODE INTEL MCP Server MCP server (johnrippy1980/god-mode-intel-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.