search_global_source_elements
Search/filter elements within a global source. No component param needed. Examples: - Find all buttons: type=
This record as markdown: /tools/webcake-storefront/search-global-source-elements.md
What search_global_source_elements does on Webcake Storefront
AI agents call search_global_source_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_source_elements is rated Low
This tool retrieves or queries data (global source elements) without any side effects. It performs filtering/search operations, which is a hallmark Read category function. There is no evidence of write, delete, execute, or financial operations. The low blast radius and non-destructive nature support a 'low' severity rating.
From the tool's definition Tool name contains 'search' and description states 'Search/filter elements within a global source' with no mention of modification, deletion, or execution capabilities. Examples show filtering by type (e.g., 'type='), a read operation.
Attacks that exploit this kind of access
The rule that runs search_global_source_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_source_elements, this is the rule to start with:
search_global_source_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_source_elements call is checked against it from then on.
Questions about search_global_source_elements
Search/filter elements within a global source. No component param needed. 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.
Register the Webcake Storefront MCP server in PolicyLayer and add a rule for search_global_source_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_source_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_source_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_source_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_source_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