move_field · Redcap MCP: Risk & Policy

WHAT IT DOES

What move_field does on Redcap

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

WHY IT NEEDS A POLICY

Why move_field needs a policy

Moving a field modifies the project structure and potentially data organization in ways that are reversible (fields can be moved again), but the action reorganizes research data schemas. This is Write-category (modifies data reversibly) rather than Destructive because field movement typically does not delete data.

From the tool's definition Tool name 'move_field' indicates structural modification of research data fields in REDCap. Server context shows tools for managing research data projects; sibling tools include 'add_field', 'delete_field', and other destructive operations, establishing this…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

move_field Rate-limited

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

FAQ

Questions about move_field

What does the move_field tool do? +

move_field. It is categorised as a Write tool in the Redcap MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on move_field? +

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

What risk level is move_field? +

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

Can I rate-limit move_field? +

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

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

move_field is provided by the Redcap MCP server (msicilia/mcp-server-redcap). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.