restore_lp_version
Undo/rollback the draft to a prior version. Find valid version IDs via list_lp_versions. This does not touch the published version.
This record as markdown: /tools/io-github-bitsandtea-postking-mcp/restore-lp-version.md
What restore_lp_version does on Postking Mcp
AI agents use restore_lp_version 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 restore_lp_version is rated Medium
This tool modifies draft content by restoring it to an earlier state. While the restoration itself is reversible (you could restore to another version), it modifies data state. It is not Destructive because the published version remains untouched and the change can be undone by restoring to a different version.
From the tool's definition restore_lp_version reverts a draft to a prior version via rollback. The description explicitly states 'This does not touch the published version,' confirming the change is reversible and isolated to draft state.
Attacks that exploit this kind of access
The rule that runs restore_lp_version 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 restore_lp_version, this is the rule to start with:
restore_lp_version 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 restore_lp_version call is checked against it from then on.
Questions about restore_lp_version
Undo/rollback the draft to a prior version. Find valid version IDs via list_lp_versions. This does not touch the published version. 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 restore_lp_version: 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.
restore_lp_version 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 restore_lp_version 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 restore_lp_version. 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.
restore_lp_version 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