Get customer search fields for the store
AI agents call customer_get_customer_search_fields to retrieve information from MCP Dynamics 365 Commerce Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves metadata about available customer search fields for the store. It is a pure query operation that returns configuration or schema information without creating, modifying, deleting, or executing any operations. The blast radius of misuse is minimal—an AI agent could only learn what search fields exist, not access actual customer data or perform actions.
From the tool's definition Tool name contains 'get' and description states 'Get customer search fields' — a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
Get customer search fields for the store. It is categorised as a Read tool in the MCP Dynamics 365 Commerce Server MCP Server, which means it retrieves data without modifying state.
Register the MCP Dynamics 365 Commerce Server MCP server in PolicyLayer and add a rule for customer_get_customer_search_fields: 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 MCP Dynamics 365 Commerce Server. Nothing to install.
customer_get_customer_search_fields 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 customer_get_customer_search_fields 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 customer_get_customer_search_fields. 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.
customer_get_customer_search_fields is provided by the MCP Dynamics 365 Commerce Server MCP server (jiantmo/mcp-commerce). 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 →