This record as markdown: /tools/io-github-bitsandtea-postking-mcp/list-landing-pages.md
What list_landing_pages does on Postking Mcp
AI agents call list_landing_pages 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.
Why list_landing_pages is rated Low
This tool retrieves and queries landing pages data with no side effects. The verb 'lists' and the absence of any mutation or destructive language clearly indicate a read-only operation. The minimal blast radius (retrieving existing data) and lack of external effects justify low severity.
From the tool's definition Tool name is 'list_landing_pages' and description states 'Lists landing pages' with no mention of modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
The rule that runs list_landing_pages 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_landing_pages, this is the rule to start with:
list_landing_pages is read-only, so it stays allowed. 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 list_landing_pages call is checked against it from then on.
Questions about list_landing_pages
Lists landing pages. Default detail=. It is categorised as a Read tool in the Postking Mcp MCP Server, which means it retrieves data without modifying state.
Register the Postking MCP server in PolicyLayer and add a rule for list_landing_pages: 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.
list_landing_pages is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_landing_pages 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 list_landing_pages. 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.
list_landing_pages 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