Update an existing account in Dynamics 365
AI agents use update-account to create or update resources in Dynamics 365 MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Dynamics 365 MCP Server environment.
This tool modifies existing account records in a business system but does not delete or irreversibly destroy data (which would make it Destructive). Updates are reversible through subsequent updates. The severity is medium because unauthorized account modifications could impact business operations and data integrity, but the blast radius is limited to account records rather than system-wide or financial operations.
From the tool's definition Tool name 'update-account' and description 'Update an existing account in Dynamics 365' indicate modification of existing data. The sibling tool 'create-account' and context of managing accounts confirms this is a reversible Write operation.
Documented attack patterns abuse exactly the kind of access update-account 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 update-account:
{
"version": "1",
"default": "deny",
"tools": {
"update-account": {
"limits": [
{
"counter": "update-account_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}update-account stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Update an existing account in Dynamics 365. It is categorised as a Write tool in the Dynamics 365 MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Dynamics 365 MCP Server MCP server in PolicyLayer and add a rule for update-account: 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.
update-account is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the update-account 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 update-account. 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.
update-account 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.