unassign_instrument_from_event · Redcap MCP: Risk & Policy

WHAT IT DOES

What unassign_instrument_from_event does on Redcap

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

The tool removes an instrument's assignment to an event, which is a reversible data modification—the assignment can be re-created. This falls under Write rather than Destructive since no data is deleted, only a relationship is removed. The empty description lowers confidence slightly, but the name and context from sibling tools clearly indicate a modification operation affecting research project structure.

From the tool's definition Tool name 'unassign_instrument_from_event' indicates it modifies the relationship between instruments and events in a REDCap project; sister tools like 'delete_file', 'delete_instrument', and 'assign_instrument_to_event' confirm this server manages research…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

unassign_instrument_from_event Rate-limited

unassign_instrument_from_event 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": {
    "unassign_instrument_from_event": {
      "limits": [
        {
          "counter": "unassign_instrument_from_event_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 unassign_instrument_from_event

What does the unassign_instrument_from_event tool do? +

unassign_instrument_from_event. 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 unassign_instrument_from_event? +

Register the Redcap MCP server in PolicyLayer and add a rule for unassign_instrument_from_event: 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 unassign_instrument_from_event? +

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

Can I rate-limit unassign_instrument_from_event? +

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

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

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