stock_count_journal_remove_transaction
Deletes the stock count journal transaction from local.
This record as markdown: /tools/jiantmo-mcp-commerce/stock-count-journal-remove-transaction.md
What stock_count_journal_remove_transaction does on MCP Dynamics 365 Commerce Server
AI agents call stock_count_journal_remove_transaction to permanently remove resources in MCP Dynamics 365 Commerce Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why stock_count_journal_remove_transaction is rated Critical
The tool explicitly deletes a stock count journal transaction. Deletion is irreversible and falls under the Destructive category. High severity because removing inventory journal transactions can corrupt audit trails and inventory accuracy.
From the tool's definition 'Deletes the stock count journal transaction from local'
Attacks that exploit this kind of access
The rule that runs stock_count_journal_remove_transaction safely
PolicyLayer is an MCP gateway: it sits between your AI agents and MCP Dynamics 365 Commerce Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For stock_count_journal_remove_transaction, this is the rule to start with:
stock_count_journal_remove_transaction is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect MCP Dynamics 365 Commerce Server, apply this rule, and every stock_count_journal_remove_transaction call is checked against it from then on.
Questions about stock_count_journal_remove_transaction
Deletes the stock count journal transaction from local. It is categorised as a Destructive tool in the MCP Dynamics 365 Commerce Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the MCP Dynamics 365 Commerce Server MCP server in PolicyLayer and add a rule for stock_count_journal_remove_transaction: 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_remove_transaction is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the stock_count_journal_remove_transaction 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_remove_transaction. 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_remove_transaction 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.
More on MCP Dynamics 365 Commerce Server, and thousands of servers like it.
Across the catalogue