seo_restore_cluster
Restore a rejected cluster back to pending_review so it can be approved again.
This record as markdown: /tools/io-github-bitsandtea-postking-mcp/seo-restore-cluster.md
What seo_restore_cluster does on Postking Mcp
AI agents use seo_restore_cluster 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 seo_restore_cluster is rated Medium
The tool changes data state (rejected → pending_review) rather than creating new data, and the change is reversible (could be rejected again). This qualifies as Write rather than Execute (no code execution) or Destructive (reversible).
From the tool's definition Tool description states 'Restore a rejected cluster back to pending_review' — this modifies the status/state of a previously rejected item to a different state, enabling reapproval. This is a reversible state change.
Attacks that exploit this kind of access
The rule that runs seo_restore_cluster 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 seo_restore_cluster, this is the rule to start with:
seo_restore_cluster 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 seo_restore_cluster call is checked against it from then on.
Questions about seo_restore_cluster
Restore a rejected cluster back to pending_review so it can be approved again. 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 seo_restore_cluster: 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.
seo_restore_cluster 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 seo_restore_cluster 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 seo_restore_cluster. 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.
seo_restore_cluster 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