search_global_section_elements
Search/filter elements within a global section (Header/Footer/block) without dumping the whole tree. Filter by type, id substring, custom_class, text, or has_bind / has_events / has_custom_class.
This record as markdown: /tools/webcake-storefront/search-global-section-elements.md
What search_global_section_elements does on Webcake Storefront
AI agents call search_global_section_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.
Why search_global_section_elements is rated Low
This tool performs a query/search operation that retrieves filtered information about existing elements within a global section. It has no side effects—it does not create, modify, delete, or execute anything. The design explicitly emphasizes searching without exporting the entire data structure, which is characteristic of a Read operation.
From the tool's definition Tool description explicitly states 'Search/filter elements' and 'without dumping the whole tree', indicating it retrieves and queries data about global section elements.
Attacks that exploit this kind of access
The rule that runs search_global_section_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_global_section_elements, this is the rule to start with:
search_global_section_elements 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 Webcake Storefront, apply this rule, and every search_global_section_elements call is checked against it from then on.
Questions about search_global_section_elements
Search/filter elements within a global section (Header/Footer/block) without dumping the whole tree. Filter by type, id substring, custom_class, text, or has_bind / has_events / has_custom_class. It is categorised as a Read tool in the Webcake Storefront MCP Server, which means it retrieves data without modifying state.
Register the Webcake Storefront MCP server in PolicyLayer and add a rule for search_global_section_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.
search_global_section_elements 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 search_global_section_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.
Set action: deny in the PolicyLayer policy for search_global_section_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.
search_global_section_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.
More on Webcake Storefront, and thousands of servers like it.
This server
Across the catalogue