qf_record_create · Qingflow MCP: Risk & Policy

WHAT IT DOES

What qf_record_create does on Qingflow

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

WHY IT NEEDS A POLICY

Why qf_record_create needs a policy

This tool creates new records in the Qingflow CRUD system, which is a reversible modification of data. It does not execute arbitrary code, delete data, or move money, so it falls squarely into the Write category. Severity is medium because creating unwanted records could require manual cleanup but has limited blast radius compared to destructive operations. Confidence is high based on clear naming and description.

From the tool's definition Tool name 'qf_record_create' and description 'Create one record' explicitly indicate data creation. The verb 'Create' and action of adding a new record to the Qingflow system are characteristic of Write operations.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

qf_record_create Rate-limited

qf_record_create 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": {
    "qf_record_create": {
      "limits": [
        {
          "counter": "qf_record_create_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 Qingflow, so you can run agents against it safely.

FAQ

Questions about qf_record_create

What does the qf_record_create tool do? +

Create one record. Supports explicit answers and ergonomic fields mapping (title or queId). It is categorised as a Write tool in the Qingflow MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on qf_record_create? +

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

What risk level is qf_record_create? +

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

Can I rate-limit qf_record_create? +

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

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

qf_record_create is provided by the Qingflow MCP server (qingflow-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.