Low Risk

list_scheduled_posts

List all scheduled posts.

How to control list_scheduled_posts ↓

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

Low Risk

This tool retrieves and displays information about scheduled posts without creating, modifying, deleting, or executing any actions. It is a read-only operation that queries existing data, making it a Read category risk with low severity.

From the tool's definition Tool name 'list_scheduled_posts' and description 'List all scheduled posts' indicate a query/retrieval operation with no modification or execution of side effects.

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

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

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_scheduled_posts": {}
  }
}

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

  1. Create a free account and register LinkedIn Intelligence MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the list_scheduled_posts tool do? +

List all scheduled posts. It is categorised as a Read tool in the LinkedIn Intelligence MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_scheduled_posts? +

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

What risk level is list_scheduled_posts? +

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

Can I rate-limit list_scheduled_posts? +

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

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

list_scheduled_posts is provided by the LinkedIn Intelligence MCP Server MCP server (southleft/linkedin-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every LinkedIn Intelligence MCP Server tool call.

Deterministic rules across all 87 LinkedIn Intelligence MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

87 LinkedIn Intelligence MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.