list_lp_versions

List all saved versions of a landing page. Default detail=

SERVERPostking Mcp SOURCEpostking-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/io-github-bitsandtea-postking-mcp/list-lp-versions.md

WHAT IT DOES

What list_lp_versions does on Postking Mcp

AI agents call list_lp_versions 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.

RISK

Why list_lp_versions is rated Low

This tool retrieves and queries historical versions of a landing page. The verb 'list' and the retrieval-only nature of querying saved versions without creating, modifying, or deleting data places this firmly in the Read category. The severity is low because accessing version history poses minimal risk—it discloses no financial data, executes no operations, and cannot damage data.

From the tool's definition Tool name 'list_lp_versions' and description 'List all saved versions of a landing page' indicate a retrieval operation with no modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_lp_versions 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_lp_versions, this is the rule to start with:

list_lp_versions Allowed

list_lp_versions is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_lp_versions": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Postking Mcp, apply this rule, and every list_lp_versions call is checked against it from then on.

FAQ

Questions about list_lp_versions

What does the list_lp_versions tool do? +

List all saved versions of a landing page. Default detail=. It is categorised as a Read tool in the Postking Mcp MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_lp_versions? +

Register the Postking MCP server in PolicyLayer and add a rule for list_lp_versions: 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.

What risk level is list_lp_versions? +

list_lp_versions is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_lp_versions? +

Yes. Add a rate_limit block to the list_lp_versions 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.

How do I block list_lp_versions completely? +

Set action: deny in the PolicyLayer policy for list_lp_versions. 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.

What MCP server provides list_lp_versions? +

list_lp_versions 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.

KEEP EXPLORING

What list_lp_versions does on Postking Mcp

Why list_lp_versions is rated Low

The rule that runs list_lp_versions safely

Questions about list_lp_versions

More on Postking, and thousands of servers like it.