linkedin_get_post

Get a LinkedIn post by its URN

SERVERScopeGate SOURCEhttps://mcp.scopegate.cloud/{api_key}

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-alifanov-scopegate/linkedin-get-post.md

WHAT IT DOES

What linkedin_get_post does on ScopeGate

AI agents call linkedin_get_post to retrieve information from ScopeGate without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why linkedin_get_post is rated Low

This tool retrieves/queries a single LinkedIn post by its unique resource name (URN). It performs no creation, modification, deletion, code execution, or financial transaction. The operation is read-only with minimal blast radius—the worst outcome is exposure of publicly or semi-public post content that an authorized agent can already access.

From the tool's definition Tool name 'linkedin_get_post' and description 'Get a LinkedIn post by its URN' indicate a retrieval operation with no modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs linkedin_get_post safely

PolicyLayer is an MCP gateway: it sits between your AI agents and ScopeGate, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For linkedin_get_post, this is the rule to start with:

linkedin_get_post Allowed

linkedin_get_post is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "linkedin_get_post": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect ScopeGate, apply this rule, and every linkedin_get_post call is checked against it from then on.

FAQ

Questions about linkedin_get_post

What does the linkedin_get_post tool do? +

Get a LinkedIn post by its URN. It is categorised as a Read tool in the ScopeGate MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on linkedin_get_post? +

Register the ScopeGate MCP server in PolicyLayer and add a rule for linkedin_get_post: 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 ScopeGate. Nothing to install.

What risk level is linkedin_get_post? +

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

Can I rate-limit linkedin_get_post? +

Yes. Add a rate_limit block to the linkedin_get_post 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 linkedin_get_post completely? +

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

linkedin_get_post is provided by the ScopeGate MCP server (https://mcp.scopegate.cloud/{api_key}). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on ScopeGate, and thousands of servers like it.

This server

All 385 ScopeGate tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →