get_current_context
Show current connection context: which site_id, API URL, session, and account info. Call this first to confirm you
This record as markdown: /tools/webcake-storefront/get-current-context.md
What get_current_context does on Webcake Storefront
AI agents call get_current_context 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_current_context is rated Low
This tool retrieves existing state/configuration data without modifying, deleting, or executing operations. It is a diagnostic read operation to confirm the current session context, equivalent to a 'whoami' or 'get_status' function. No data is created, modified, or destroyed, and no external operations are triggered.
From the tool's definition Tool name and description indicate it 'Show[s] current connection context' and retrieves 'site_id, API URL, session, and account info' — purely informational query with no side effects.
Attacks that exploit this kind of access
The rule that runs get_current_context 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_current_context, this is the rule to start with:
get_current_context 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_current_context call is checked against it from then on.
Questions about get_current_context
Show current connection context: which site_id, API URL, session, and account info. Call this first to confirm you. 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_current_context: 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_current_context 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_current_context 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_current_context. 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_current_context 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