Gets a stock count journal by journal id.
AI agents call stock_count_journal_get_entity_by_key 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 performs a lookup operation that retrieves an existing stock count journal record using a key parameter. It does not create, modify, delete, or execute operations. The read-only nature and straightforward data retrieval classifies it as a Read operation with low severity and blast radius.
From the tool's definition Tool name 'stock_count_journal_get_entity_by_key' uses the 'get' verb and description states 'Gets a stock count journal' — retrieves data by identifier with no modification or side effects.
Attacks that exploit this kind of access
Gets a stock count journal by journal id. 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 stock_count_journal_get_entity_by_key: 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.
stock_count_journal_get_entity_by_key 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 stock_count_journal_get_entity_by_key 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 stock_count_journal_get_entity_by_key. 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.
stock_count_journal_get_entity_by_key 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 →