search_posts

THE RISK

Low Risk

Why search_posts needs a policy

This tool retrieves or queries LinkedIn post data based on keywords and supports pagination for browsing results. It performs no modifications, deletions, or external operations—it is a pure read/search operation. The low severity reflects minimal risk of harm even if an AI agent misuses it, as search queries cannot damage data or systems.

From the tool's definition Tool name 'search_posts' and description 'Search LinkedIn posts with keywords and optional pagination' indicate query/retrieval operations with no side effects.

Documented attack patterns abuse exactly the kind of access search_posts gives an agent:

POLICY

How to control search_posts

PolicyLayer is an MCP gateway — it sits between your AI agents and LinkedIn-Posts-Hunter-MCP-Server, and nothing reaches the server without passing your rules. This is the rule we recommend for search_posts:

policy.json

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

search_posts is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register LinkedIn-Posts-Hunter-MCP-Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about search_posts

What does the search_posts tool do? +

Search LinkedIn posts with keywords and optional pagination. It is categorised as a Read tool in the LinkedIn-Posts-Hunter-MCP-Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on search_posts? +

Register the LinkedIn-Posts-Hunter-MCP-Server MCP server in PolicyLayer and add a rule for search_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 LinkedIn-Posts-Hunter-MCP-Server. Nothing to install.

What risk level is search_posts? +

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

Can I rate-limit search_posts? +

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

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

search_posts is provided by the LinkedIn-Posts-Hunter-MCP-Server MCP server (kevin-weitgenant/linkedin-posts-hunter-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every LinkedIn-Posts-Hunter-MCP-Server tool call.

Start from LinkedIn-Posts-Hunter-MCP-Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →