invoke_tool

Run any WebCake tool by exact name with its arguments (discover names + schemas via search_tools). Arguments are validated before running. Use this for tools that are not loaded natively.

SERVERWebcake Storefront SOURCEwebcake-storefront-mcp
High RISK CLASS
Category Execute
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/webcake-storefront/invoke-tool.md

What invoke_tool does on Webcake Storefront

AI agents invoke invoke_tool to trigger actions in Webcake Storefront. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

Why invoke_tool is rated High

This is a meta-tool that allows execution of any tool exposed by the WebCake server. Given the sibling tools include destructive operations (delete, purge patterns likely exist), financial operations (orders, subscriptions), and write operations (page CRUD, product management), and this tool bypasses the native loading constraint, it represents a critical Execute risk.

From the tool's definition Tool description states 'Run any WebCake tool by exact name with its arguments' — this is a generic execution wrapper that permits invoking arbitrary tools on the server without native loading constraints.

Questions about invoke_tool

What does the invoke_tool tool do? +

Run any WebCake tool by exact name with its arguments (discover names + schemas via search_tools). Arguments are validated before running. Use this for tools that are not loaded natively. It is categorised as a Execute tool in the Webcake Storefront MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on invoke_tool? +

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

invoke_tool is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit invoke_tool? +

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

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

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