Gets data store name.
AI agents call async_service_get_terminal_data_store_name 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 configuration or metadata about a data store name. It performs a simple read operation with no side effects, no data modification, no code execution, and no destructive actions. The minimal scope (fetching a single data store name) and read-only nature classify this as a low-severity Read operation.
From the tool's definition Tool name 'async_service_get_terminal_data_store_name' uses the 'get' verb, and description states 'Gets data store name' indicating data retrieval without modification.
Attacks that exploit this kind of access
Gets data store name. 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 async_service_get_terminal_data_store_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 MCP Dynamics 365 Commerce Server. Nothing to install.
async_service_get_terminal_data_store_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 async_service_get_terminal_data_store_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 async_service_get_terminal_data_store_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.
async_service_get_terminal_data_store_name 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 →