find_customer

Find a customer by ID, phone number, or email

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/find-customer.md

WHAT IT DOES

What find_customer does on Webcake Storefront

AI agents call find_customer 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 find_customer is rated Low

This tool retrieves customer information without side effects. It performs a search/lookup operation, matching the Read category definition. Severity is low because customer lookup alone poses minimal risk; the queried data may be sensitive but the tool does not modify, delete, or trigger external operations. Confidence is high given the clear query intent in both name and description.

From the tool's definition Tool name 'find_customer' and description 'Find a customer by ID, phone number, or email' indicate a query/lookup operation with no modification or deletion of data.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

find_customer Allowed

find_customer 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": {
    "find_customer": {}
  }
}

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 find_customer call is checked against it from then on.

FAQ

Questions about find_customer

What does the find_customer tool do? +

Find a customer by ID, phone number, or email. 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 find_customer? +

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

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

Can I rate-limit find_customer? +

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

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

find_customer 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

aiva_get_customer on AIVA MCP Server → The MCP Attack Database →

Guides

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