set_side_page_state
Publish or unpublish a side page. Set published=true to make it live, false to pull it back to draft. This writes in-place immediately — there is no version history or undo.
This record as markdown: /tools/io-github-bitsandtea-postking-mcp/set-side-page-state.md
What set_side_page_state does on Postking Mcp
AI agents use set_side_page_state 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_side_page_state is rated Medium
This tool modifies live content state (published/unpublished), making it a Write operation. It is classified as 'high' severity rather than 'critical' because the action is technically reversible (one can toggle published back to false), though the lack of version history or undo means changes take effect immediately without recovery options.
From the tool's definition The tool description states it 'Publish or unpublish a side page' and 'writes in-place immediately — there is no version history or undo.' This is a reversible modification (toggling published state), but has immediate production impact.
Attacks that exploit this kind of access
The rule that runs set_side_page_state 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_side_page_state, this is the rule to start with:
set_side_page_state 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_side_page_state call is checked against it from then on.
Questions about set_side_page_state
Publish or unpublish a side page. Set published=true to make it live, false to pull it back to draft. This writes in-place immediately — there is no version history or undo. 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_side_page_state: 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_side_page_state 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_side_page_state 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_side_page_state. 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_side_page_state 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