get_page_versions

View version history of a page

SERVERWebcake Storefront SOURCEwebcake-storefront-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/webcake-storefront/get-page-versions.md

WHAT IT DOES

What get_page_versions does on Webcake Storefront

AI agents call get_page_versions to retrieve information from Webcake Storefront without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why get_page_versions is rated Low

This tool retrieves historical version information about a page, which is a query/lookup operation. There is no data creation, modification, deletion, code execution, or financial impact. The blast radius of misuse is minimal—an unauthorized actor could view page history but cannot alter or delete data.

From the tool's definition Tool name 'get_page_versions' and description 'View version history of a page' indicate a read-only retrieval operation with no modifications or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_page_versions safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Webcake Storefront, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_page_versions, this is the rule to start with:

get_page_versions Allowed

get_page_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": {
    "get_page_versions": {}
  }
}

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

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

FAQ

Questions about get_page_versions

What does the get_page_versions tool do? +

View version history of a page. It is categorised as a Read tool in the Webcake Storefront MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_page_versions? +

Register the Webcake Storefront MCP server in PolicyLayer and add a rule for get_page_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 Webcake Storefront. Nothing to install.

What risk level is get_page_versions? +

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

Can I rate-limit get_page_versions? +

Yes. Add a rate_limit block to the get_page_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 get_page_versions completely? +

Set action: deny in the PolicyLayer policy for get_page_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 get_page_versions? +

get_page_versions is provided by the Webcake Storefront MCP server (webcake-storefront-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Webcake Storefront, and thousands of servers like it.

This server

All 287 Webcake Storefront tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →