set_post_cards
Bulk-replace all carousel cards for a post. Provide a full array of card objects with title, body, and optional number.
This record as markdown: /tools/io-github-bitsandtea-postking-mcp/set-post-cards.md
What set_post_cards does on Postking Mcp
AI agents use set_post_cards to create or update resources in Postking Mcp, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Postking Mcp environment.
Why set_post_cards is rated Medium
This tool creates or modifies data (carousel card content) but does not irreversibly delete it, execute code, or commit financial transactions. The bulk nature and replacement semantics elevate severity from low to medium, as it could affect multiple content cards in a single operation, but the change is reversible through a subsequent edit.
From the tool's definition Tool description states 'Bulk-replace all carousel cards for a post' — this modifies existing post content via a reversible write operation. The word 'replace' indicates data modification, and 'carousel cards' are content elements that can be edited back.
Attacks that exploit this kind of access
The rule that runs set_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 set_post_cards, this is the rule to start with:
set_post_cards stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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 set_post_cards call is checked against it from then on.
Questions about set_post_cards
Bulk-replace all carousel cards for a post. Provide a full array of card objects with title, body, and optional number. It is categorised as a Write tool in the Postking Mcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Postking MCP server in PolicyLayer and add a rule for set_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.
set_post_cards is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the set_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 set_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.
set_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