search_page_elements

Search/filter elements within a page source. Returns matching elements with full detail (id, type, style, text, classes, etc.). Examples: - Find all buttons: type=

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/search-page-elements.md

WHAT IT DOES

What search_page_elements does on Webcake Storefront

AI agents call search_page_elements 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 search_page_elements is rated Low

The tool reads and searches page element data to return details (id, type, style, text, classes, etc.) with no capability to create, modify, delete, or execute operations. It is purely informational retrieval with no side effects, making it a Read category tool with low severity risk.

From the tool's definition Tool description states 'Search/filter elements within a page source. Returns matching elements' — this is a query/search operation that retrieves data without modification.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

search_page_elements Allowed

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

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 search_page_elements call is checked against it from then on.

FAQ

Questions about search_page_elements

What does the search_page_elements tool do? +

Search/filter elements within a page source. Returns matching elements with full detail (id, type, style, text, classes, etc.). Examples: - Find all buttons: type=. 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 search_page_elements? +

Register the Webcake Storefront MCP server in PolicyLayer and add a rule for search_page_elements: 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 search_page_elements? +

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

Can I rate-limit search_page_elements? +

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

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

search_page_elements 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

search_torrents on M-Team MCP Server →aiva_search_customers on AIVA MCP Server →search_channel on YouTube MCP Server →hybrid_search on Azure AI Agent Service + Azure AI Search MCP Server → The MCP Attack Database →

Guides

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