Get customer IDs by using a customer's full name
AI agents call get_customer_ids_by_name to retrieve information from E-commerce MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves customer IDs based on a search parameter (name). It performs a read-only query against customer data with no side effects, reversible actions, code execution, or financial impact. The operation is informational and non-destructive. Severity is low because customer IDs are typically non-sensitive identifiers and the query has minimal blast radius if misused.
From the tool's definition Tool name 'get_customer_ids_by_name' and description 'Get customer IDs by using a customer's full name' indicate a query operation that retrieves data without modification.
Attacks that exploit this kind of access
Get customer IDs by using a customer's full name. It is categorised as a Read tool in the E-commerce MCP Server MCP Server, which means it retrieves data without modifying state.
Register the E-commerce MCP Server MCP server in PolicyLayer and add a rule for get_customer_ids_by_name: 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 E-commerce MCP Server. Nothing to install.
get_customer_ids_by_name 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_customer_ids_by_name 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_customer_ids_by_name. 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_customer_ids_by_name is provided by the E-commerce MCP Server MCP server (kodymullins/mcp_test). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →