Get zip codes filtered by location.
AI agents call zipcodes_get_zip_codes 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 zip code data based on location filters. It performs a query/lookup operation without creating, modifying, deleting, or executing any operations. The action is purely informational and read-only, making it a Read category tool with low severity since unauthorized access to public zip code information poses minimal risk.
From the tool's definition Tool name 'zipcodes_get_zip_codes' with description 'Get zip codes filtered by location' indicates a retrieval operation with no side effects.
Attacks that exploit this kind of access
Get zip codes filtered by location. 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 zipcodes_get_zip_codes: 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.
zipcodes_get_zip_codes 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 zipcodes_get_zip_codes 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 zipcodes_get_zip_codes. 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.
zipcodes_get_zip_codes 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 →