Fetch total count of orders from Saleor GraphQL API.
AI agents call order_count to retrieve information from Saleor MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a simple data query to retrieve order count information. It has no capability to modify, delete, or execute operations. The read-only nature of the Saleor MCP server integration and the query-only semantics of 'Fetch...count' confirm this is a Read category risk. Severity is low because retrieving aggregate count data has minimal blast radius even if misused by an agent.
From the tool's definition Tool description states 'Fetch total count of orders' - a retrieval operation with no modification. Server description emphasizes 'read-only GraphQL API integration.' The tool is listed among sibling tools (customers, products, orders, stocks) that are all…
Documented attack patterns abuse exactly the kind of access order_count gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Saleor MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for order_count:
{
"version": "1",
"default": "deny",
"tools": {
"order_count": {}
}
}order_count is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Fetch total count of orders from Saleor GraphQL API. It is categorised as a Read tool in the Saleor MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Saleor MCP Server MCP server in PolicyLayer and add a rule for order_count: 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 Saleor MCP Server. Nothing to install.
order_count 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 order_count 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 order_count. 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.
order_count is provided by the Saleor MCP Server MCP server (saleor/saleor-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Saleor MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
8 Saleor MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.