Gets a Warehouse by identifier.
AI agents call warehouse_get_warehouse_by_id 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 queries and retrieves warehouse data by ID. It performs no modifications, deletions, executions, or financial operations. The action is purely informational and read-only, consistent with standard data retrieval operations. The blast radius of misuse is minimal—an agent could only access existing warehouse information.
From the tool's definition Tool name 'warehouse_get_warehouse_by_id' and description 'Gets a Warehouse by identifier' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
Gets a Warehouse by identifier. 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 warehouse_get_warehouse_by_id: 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.
warehouse_get_warehouse_by_id 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 warehouse_get_warehouse_by_id 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 warehouse_get_warehouse_by_id. 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.
warehouse_get_warehouse_by_id 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 →