get_global_source_element

Get full detail of a single element (style, config, specials, events, bindings, responsive, children).

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-global-source-element.md

What get_global_source_element does on Webcake Storefront

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

This tool retrieves configuration and metadata about a single UI element (style, config, specials, events, bindings, responsive, children). It performs no creation, modification, deletion, code execution, or financial operations. It is a straightforward read operation querying element properties in the storefront builder.

From the tool's definition Tool name 'get_global_source_element' uses the 'get' verb and description states 'Get full detail of a single element', indicating retrieval of data without modification or side effects.

Questions about get_global_source_element

What does the get_global_source_element tool do? +

Get full detail of a single element (style, config, specials, events, bindings, responsive, children). 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_global_source_element? +

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

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

Can I rate-limit get_global_source_element? +

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

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

get_global_source_element 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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Webcake Storefront's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.