Gets affiliations.
AI agents call non_sales_tender_get_affiliations 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 queries and retrieves affiliation data from the Dynamics 365 Commerce system without creating, modifying, deleting, or executing any operations. It is a standard read operation returning existing data. Low severity because retrieval of affiliation information poses minimal risk; the blast radius of misuse is limited to unauthorized data access rather than system corruption or financial impact.
From the tool's definition Tool name uses 'get_' prefix and description states 'Gets affiliations' — clearly a retrieval operation with no modification or deletion capability.
Attacks that exploit this kind of access
Gets affiliations. 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 non_sales_tender_get_affiliations: 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.
non_sales_tender_get_affiliations 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 non_sales_tender_get_affiliations 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 non_sales_tender_get_affiliations. 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.
non_sales_tender_get_affiliations 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 →