azure_sql_update_record · Azure SQL MCP Server MCP

WHAT IT DOES

What azure_sql_update_record does on Azure SQL MCP Server

AI agents use azure_sql_update_record to create or update resources in Azure SQL MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Azure SQL MCP Server environment.

WHY IT NEEDS A POLICY

Why azure_sql_update_record needs a policy

This tool creates or modifies data reversibly—a characteristic of the Write category. It updates existing records rather than destroying them (would be Destructive) or executing arbitrary queries (would be Execute).

From the tool's definition Tool name `azure_sql_update_record` explicitly indicates modification of existing records in an Azure SQL database. The server description confirms this tool supports 'CRUD operations' and 'record management'.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

azure_sql_update_record Rate-limited

azure_sql_update_record 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "azure_sql_update_record": {
      "limits": [
        {
          "counter": "azure_sql_update_record_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Azure SQL MCP Server, so you can run agents against it safely.

FAQ

Questions about azure_sql_update_record

What does the azure_sql_update_record tool do? +

azure_sql_update_record. It is categorised as a Write tool in the Azure SQL MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on azure_sql_update_record? +

Register the Azure SQL MCP Server MCP server in PolicyLayer and add a rule for azure_sql_update_record: 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 SQL MCP Server. Nothing to install.

What risk level is azure_sql_update_record? +

azure_sql_update_record is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit azure_sql_update_record? +

Yes. Add a rate_limit block to the azure_sql_update_record 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.

How do I block azure_sql_update_record completely? +

Set action: deny in the PolicyLayer policy for azure_sql_update_record. 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.

What MCP server provides azure_sql_update_record? +

azure_sql_update_record is provided by the Azure SQL MCP Server MCP server (lostspace003/copilot-studio-azure-sql-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.