List queued posts.
AI agents call list_queue to retrieve information from LinkedIn Poster without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays information about queued posts without modifying, deleting, or executing any actions. It is a straightforward data retrieval operation. Severity is low because reading queued post metadata poses minimal risk—it does not expose sensitive personal data beyond what the authenticated user already controls, and it cannot be misused to cause financial, destructive, or other significant…
From the tool's definition Tool name 'list_queue' and description 'List queued posts' indicate a query/retrieval operation with no side effects. The verb 'list' is explicitly read-only.
Attacks that exploit this kind of access
List queued posts. It is categorised as a Read tool in the LinkedIn Poster MCP Server, which means it retrieves data without modifying state.
Register the LinkedIn Poster MCP server in PolicyLayer and add a rule for list_queue: 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 Poster. Nothing to install.
list_queue 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 list_queue 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 list_queue. 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.
list_queue is provided by the LinkedIn Poster MCP server (urfanazad/posterlinkedin). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the 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 →