insert_record · Insecure MCP Demo MCP: Risk & Policy

WHAT IT DOES

What insert_record does on Insecure MCP Demo

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

WHY IT NEEDS A POLICY

Why insert_record needs a policy

This tool creates or modifies data reversibly (matching Write category), but operates in a deliberately vulnerable environment where SQL injection is a documented risk. While the tool itself is Write-level, the severe underlying vulnerabilities elevate practical risk to high severity.

From the tool's definition Tool name 'insert_record' and description 'Insert a new record into the database' indicate data creation/modification.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

insert_record Rate-limited

insert_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": {
    "insert_record": {
      "limits": [
        {
          "counter": "insert_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 Insecure MCP Demo, so you can run agents against it safely.

FAQ

Questions about insert_record

What does the insert_record tool do? +

Insert a new record into the database. It is categorised as a Write tool in the Insecure MCP Demo MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on insert_record? +

Register the Insecure MCP Demo MCP server in PolicyLayer and add a rule for insert_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 Insecure MCP Demo. Nothing to install.

What risk level is insert_record? +

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

Can I rate-limit insert_record? +

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

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

insert_record is provided by the Insecure MCP Demo MCP server (kenhuangus/mcp-vulnerable-server-demo). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.