update_model_deployment
AI agents use update_model_deployment to create or update resources in Azure AI Agent Service MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Azure AI Agent Service MCP Server environment.
The tool name strongly suggests updating/modifying an existing model deployment configuration in Azure AI infrastructure. This is reversible (can be rolled back or updated again), placing it in Write rather than Destructive. However, confidence is reduced due to empty description. Severity is high because misconfigured model deployments could affect service availability or expose unauthorized access to AI models.
From the tool's definition Tool name is 'update_model_deployment' which indicates modification of deployment configuration. Description is empty, limiting certainty.
Documented attack patterns abuse exactly the kind of access update_model_deployment gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Azure AI Agent Service MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for update_model_deployment:
{
"version": "1",
"default": "deny",
"tools": {
"update_model_deployment": {
"limits": [
{
"counter": "update_model_deployment_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} update_model_deployment 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_model_deployment. It is categorised as a Write tool in the Azure AI Agent Service MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Azure AI Agent Service MCP Server MCP server in PolicyLayer and add a rule for update_model_deployment: 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 Azure AI Agent Service MCP Server. Nothing to install.
update_model_deployment 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_model_deployment 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_model_deployment. 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_model_deployment is provided by the Azure AI Agent Service MCP Server MCP server (microsoft-foundry/mcp-foundry). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Azure AI Agent Service 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.
28 Azure AI Agent Service MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.