count_orders_by_status

Get order count grouped by status. Useful for dashboard overview

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/count-orders-by-status.md

WHAT IT DOES

What count_orders_by_status does on Webcake Storefront

AI agents call count_orders_by_status 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.

RISK

Why count_orders_by_status is rated Low

This tool retrieves aggregated order data for display purposes only. It queries existing information without creating, modifying, deleting, or executing any side effects. No financial transactions, code execution, or data mutations occur. This is a straightforward Read classification with low risk.

From the tool's definition Tool name 'count_orders_by_status' and description 'Get order count grouped by status' indicate a query/retrieval operation with no modification capability. The phrase 'Useful for dashboard overview' confirms this is a read-only analytics function.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs count_orders_by_status 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 count_orders_by_status, this is the rule to start with:

count_orders_by_status Allowed

count_orders_by_status is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "count_orders_by_status": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Webcake Storefront, apply this rule, and every count_orders_by_status call is checked against it from then on.

FAQ

Questions about count_orders_by_status

What does the count_orders_by_status tool do? +

Get order count grouped by status. Useful for dashboard overview. 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 count_orders_by_status? +

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

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

Can I rate-limit count_orders_by_status? +

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

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

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

KEEP EXPLORING

More on Webcake Storefront, and thousands of servers like it.

This server

All 287 Webcake Storefront tools →

Across the catalogue

shopify_get_orders on AIVA MCP Server →claude_git_status on Claude Bridge →get_task_status on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →