Retrieve saved LinkedIn posts with pagination.
AI agents call get_saved_posts to retrieve information from Linkedin-Profile-Analyzer without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves existing LinkedIn posts that have been saved, enabling users to fetch and paginate through data without creating, modifying, or deleting anything. The operation has no side effects beyond data access, fitting the 'Read' category.
From the tool's definition Tool name 'get_saved_posts' and description 'Retrieve saved LinkedIn posts with pagination' indicate data retrieval with no modification capability. The verb 'Retrieve' and lack of any write/delete/execute operations confirm this is a read-only query.
Documented attack patterns abuse exactly the kind of access get_saved_posts gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Linkedin-Profile-Analyzer, and nothing reaches the server without passing your rules. This is the rule we recommend for get_saved_posts:
{
"version": "1",
"default": "deny",
"tools": {
"get_saved_posts": {}
}
}get_saved_posts 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.
Retrieve saved LinkedIn posts with pagination. It is categorised as a Read tool in the Linkedin-Profile-Analyzer MCP Server, which means it retrieves data without modifying state.
Register the Linkedin-Profile-Analyzer MCP server in PolicyLayer and add a rule for get_saved_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-Profile-Analyzer. Nothing to install.
get_saved_posts 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_saved_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.
Set action: deny in the PolicyLayer policy for get_saved_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.
get_saved_posts is provided by the Linkedin-Profile-Analyzer MCP server (rugvedp/linkedin-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 5 Linkedin-Profile-Analyzer tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
5 Linkedin-Profile-Analyzer tools catalogued and risk-classified — across an index of 42,500+ MCP servers.