AI agents call fetch-accounts to retrieve information from Dynamics 365 MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Fetching or retrieving data from a system is a Read operation with no side effects. The tool retrieves existing account information without creating, modifying, or deleting data. Severity is low because account data retrieval in a CRM system typically has limited blast radius—it may expose business information but does not enable destructive or financial actions.
From the tool's definition Tool name 'fetch-accounts' and description 'Fetch accounts from Dynamics 365' indicate data retrieval without modification. Sibling tools like 'create-account' and 'update-account' are distinct, confirming this tool is read-only.
Documented attack patterns abuse exactly the kind of access fetch-accounts gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Dynamics 365 MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for fetch-accounts:
{
"version": "1",
"default": "deny",
"tools": {
"fetch-accounts": {}
}
}fetch-accounts is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Fetch accounts from Dynamics 365. It is categorised as a Read tool in the Dynamics 365 MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Dynamics 365 MCP Server MCP server in PolicyLayer and add a rule for fetch-accounts: 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 MCP Server. Nothing to install.
fetch-accounts 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 fetch-accounts 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 fetch-accounts. 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.
fetch-accounts is provided by the Dynamics 365 MCP Server MCP server (srikanth-paladugula/mcp-dynamics365-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Dynamics 365 MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
5 Dynamics 365 MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.