record_feedback · MSSQL MCP Server MCP: Risk & Policy

WHAT IT DOES

What record_feedback does on MSSQL MCP Server

AI agents use record_feedback 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_feedback needs a policy

The tool writes feedback data to persistent storage, which is a reversible write operation. It creates new records but does not execute queries, delete data, or involve financial transactions. Severity is medium because an AI agent could potentially misuse this to inject false feedback or spam the system, but the blast radius is limited compared to destructive or financial operations.

From the tool's definition 'Persist user feedback' indicates writing/creating data to a storage system

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

record_feedback Rate-limited

record_feedback 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_feedback": {
      "limits": [
        {
          "counter": "record_feedback_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_feedback

What does the record_feedback tool do? +

Persist user feedback for a SQL copilot interaction. 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_feedback? +

Register the MSSQL MCP Server MCP server in PolicyLayer and add a rule for record_feedback: 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_feedback? +

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

Can I rate-limit record_feedback? +

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

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

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