Round amount by tender type
AI agents use tender_types_round_amount_by_tender_type to create or update resources in MCP Dynamics 365 Commerce Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Dynamics 365 Commerce Server environment.
The tool transforms a numeric value (amount) based on business rules (tender type), which constitutes a reversible data modification. It does not delete data (not Destructive), does not execute arbitrary code (not Execute), does not move money (not Financial), and is not a simple read operation (not Read).
From the tool's definition Tool name indicates 'round_amount_by_tender_type' which modifies/transforms a monetary amount according to tender type rules.
Attacks that exploit this kind of access
Round amount by tender type. It is categorised as a Write tool in the MCP Dynamics 365 Commerce Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Dynamics 365 Commerce Server MCP server in PolicyLayer and add a rule for tender_types_round_amount_by_tender_type: 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.
tender_types_round_amount_by_tender_type is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the tender_types_round_amount_by_tender_type 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 tender_types_round_amount_by_tender_type. 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.
tender_types_round_amount_by_tender_type 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 →