Gets the total count of records for a given OData entity.
AI agents call getEntityCount 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.
This tool queries metadata about entity counts without creating, modifying, deleting, or executing operations on data. It is a simple read operation with minimal blast radius if misused—an agent could retrieve record counts for any entity, but cannot alter or access sensitive data itself.
From the tool's definition Tool name 'getEntityCount' and description 'Gets the total count of records for a given OData entity' indicate a retrieval operation with no modification or deletion of data.
Attacks that exploit this kind of access
Gets the total count of records for a given OData entity. 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 getEntityCount: 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.
getEntityCount 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 getEntityCount 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 getEntityCount. 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.
getEntityCount 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 →