Get credit memo by identifier
AI agents call credit_memo_get_credit_memo_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 retrieves an existing credit memo record by its ID. It performs a query/lookup operation that returns data without modifying, creating, deleting, or executing any external actions. The lack of action verbs like 'create', 'update', 'delete', or 'execute' confirms it is a safe read-only operation with minimal blast radius.
From the tool's definition Tool name contains 'get' and description states 'Get credit memo by identifier' — a retrieval operation with no side effects.
Attacks that exploit this kind of access
Get credit memo 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 credit_memo_get_credit_memo_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.
credit_memo_get_credit_memo_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 credit_memo_get_credit_memo_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 credit_memo_get_credit_memo_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.
credit_memo_get_credit_memo_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 →