qf.records.mutate · Qingflow MCP: Risk & Policy

WHAT IT DOES

What qf.records.mutate does on Qingflow

AI agents use qf.records.mutate 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.records.mutate needs a policy

This tool creates or modifies records reversibly. It does not delete data (Destructive), execute arbitrary code (Execute), or move money (Financial). While high severity due to potential data modification impact in a business workflow system, it remains in the Write category as the operations described are not irreversible.

From the tool's definition Tool description states 'Canonical write entry for create/update operations.' The name 'mutate' combined with the descriptor indicates reversible data modification without deletion.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

qf.records.mutate Rate-limited

qf.records.mutate 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.records.mutate": {
      "limits": [
        {
          "counter": "qf.records.mutate_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.records.mutate

What does the qf.records.mutate tool do? +

Canonical write entry for create/update operations. 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.records.mutate? +

Register the Qingflow MCP server in PolicyLayer and add a rule for qf.records.mutate: 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.records.mutate? +

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

Can I rate-limit qf.records.mutate? +

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

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

qf.records.mutate 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.