AI agents call export_events to retrieve information from Redcap without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool exports/retrieves event information from REDCap, which is a read-only operation. It queries and returns existing data without creating, modifying, or deleting anything. Low severity as it only reads project structure data.
From the tool's definition 'Export events' - retrieves event data from a longitudinal REDCap project with no modification of data
Attacks that exploit this kind of access
Export events for a longitudinal REDCap project. It is categorised as a Read tool in the Redcap MCP Server, which means it retrieves data without modifying state.
Register the Redcap MCP server in PolicyLayer and add a rule for export_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.
export_events is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the export_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.
Set action: deny in the PolicyLayer policy for export_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.
export_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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →