record_audit_event · MSSQL MCP Server MCP: Risk & Policy

WHAT IT DOES

What record_audit_event does on MSSQL MCP Server

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

WHY IT NEEDS A POLICY

Why record_audit_event needs a policy

The tool writes/creates a new audit record in a persistent store. This is a Write operation (creating data) rather than Read. It is not Destructive (no deletion), not Execute (no arbitrary code), and not Financial. Severity is medium because while audit tampering could obscure malicious activity, the tool itself only appends structured records rather than modifying or deleting existing data.

From the tool's definition Persist a structured audit event to the SQL Server audit store

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

record_audit_event Rate-limited

record_audit_event 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": {
    "record_audit_event": {
      "limits": [
        {
          "counter": "record_audit_event_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 MSSQL MCP Server, so you can run agents against it safely.

FAQ

Questions about record_audit_event

What does the record_audit_event tool do? +

Persist a structured audit event to the SQL Server audit store. It is categorised as a Write tool in the MSSQL 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 record_audit_event? +

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

What risk level is record_audit_event? +

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

Can I rate-limit record_audit_event? +

Yes. Add a rate_limit block to the record_audit_event 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 record_audit_event completely? +

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

record_audit_event is provided by the MSSQL MCP Server MCP server (mortada7-11/mssql-mcpo-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.