get_site_custom_code
Get custom code of the site (CSS/JS). Two modes: - Default: returns ALL 4 code fields (full content) - With field filter: returns only the specified field(s) — saves tokens when you only need CSS or JS Add include_guide=true on first call to get the coding guide
This record as markdown: /tools/webcake-storefront/get-site-custom-code.md
What get_site_custom_code does on Webcake Storefront
AI agents call get_site_custom_code 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_site_custom_code is rated Low
This tool retrieves existing custom code (CSS/JS) from a site without modifying, executing, or deleting anything. It is a pure data retrieval operation with configurable output filtering. The read-only nature and lack of side effects clearly place it in the Read category with low severity, as exposure would only allow viewing site styling and scripting code, not altering site behavior or data.
From the tool's definition Tool description explicitly states it 'returns' custom code with options to filter fields. The verb 'Get' and 'returns' indicate retrieval only. No modification, deletion, or execution capabilities are mentioned.
Attacks that exploit this kind of access
The rule that runs get_site_custom_code 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_site_custom_code, this is the rule to start with:
get_site_custom_code 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 get_site_custom_code call is checked against it from then on.
Questions about get_site_custom_code
Get custom code of the site (CSS/JS). Two modes: - Default: returns ALL 4 code fields (full content) - With field filter: returns only the specified field(s) — saves tokens when you only need CSS or JS Add include_guide=true on first call to get the coding guide. 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 get_site_custom_code: 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.
get_site_custom_code 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 get_site_custom_code 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 get_site_custom_code. 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.
get_site_custom_code 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