Executes a generic GET request against a Dynamics 365 OData entity. The entity name does not need to be case-perfect. Responses are paginated.
AI agents call odataQuery to retrieve information from Dynamics 365 Finance & Operations MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Although this is primarily a Read operation, the severity is medium rather than low because: (1) it provides generic access to potentially sensitive business data in Dynamics 365 F&O (customers, financial records, system users); (2) pagination and broad entity access mean an agent could systematically extract large datasets; (3) the generic nature of the query could enable enumeration attacks across multiple entity…
From the tool's definition Tool description states it 'Executes a generic GET request against a Dynamics 365 OData entity' and 'Responses are paginated.' The GET method and read-only OData queries indicate retrieval without modification.
Attacks that exploit this kind of access
Executes a generic GET request against a Dynamics 365 OData entity. The entity name does not need to be case-perfect. Responses are paginated. It is categorised as a Read tool in the Dynamics 365 Finance & Operations MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Dynamics 365 Finance & Operations MCP Server MCP server in PolicyLayer and add a rule for odataQuery: 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 Dynamics 365 Finance & Operations MCP Server. Nothing to install.
odataQuery 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 odataQuery 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 odataQuery. 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.
odataQuery is provided by the Dynamics 365 Finance & Operations MCP Server MCP server (sahib-sawhney-wh/fno-mcp-server). 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 →