import_repeating_instruments_events

WHAT IT DOES

What import_repeating_instruments_events does on Redcap

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

The tool likely creates or modifies the structure of repeating instruments and events within a REDCap project—a reversible data/configuration change rather than deletion or financial action. However, confidence is moderate (0.72) because the description is empty, making the exact behavior somewhat ambiguous.

From the tool's definition Tool name 'import_repeating_instruments_events' suggests creating/modifying repeating instrument and event configurations in REDCap. Parent server description indicates this tool manages research data and projects.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

import_repeating_instruments_events Rate-limited

import_repeating_instruments_events 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": {
    "import_repeating_instruments_events": {
      "limits": [
        {
          "counter": "import_repeating_instruments_events_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 import_repeating_instruments_events

What does the import_repeating_instruments_events tool do? +

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

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

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

Can I rate-limit import_repeating_instruments_events? +

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

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

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