list_post_cards
List the carousel cards attached to a post. Cards are used for LinkedIn carousel / PDF generation. Returns {index,title} by default; use detail=
This record as markdown: /tools/io-github-bitsandtea-postking-mcp/list-post-cards.md
What list_post_cards does on Postking Mcp
AI agents call list_post_cards to retrieve information from Postking Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_post_cards is rated Low
This tool retrieves metadata about existing carousel cards without performing any write, execute, or destructive operations. It is a straightforward data query with no side effects, fitting the 'Read' category. The severity is low because unauthorized listing of post cards poses minimal risk—the information retrieved is metadata about content structure rather than sensitive data exfiltration or system manipulation.
From the tool's definition Tool name 'list_post_cards' and description explicitly states 'List the carousel cards attached to a post.' The verb 'list' indicates a query/retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs list_post_cards safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Postking Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_post_cards, this is the rule to start with:
list_post_cards is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Postking Mcp, apply this rule, and every list_post_cards call is checked against it from then on.
Questions about list_post_cards
List the carousel cards attached to a post. Cards are used for LinkedIn carousel / PDF generation. Returns {index,title} by default; use detail=. It is categorised as a Read tool in the Postking Mcp MCP Server, which means it retrieves data without modifying state.
Register the Postking MCP server in PolicyLayer and add a rule for list_post_cards: 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 Postking Mcp. Nothing to install.
list_post_cards 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_post_cards 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_post_cards. 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_post_cards is provided by the Postking MCP server (postking-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Postking, and thousands of servers like it.
This server
Across the catalogue