AI agents call get_instrument_event_mappings 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.
This tool retrieves instrument-to-event mappings in a REDCap project. It performs a read-only query operation to return configuration data. No data is created, modified, deleted, or executed. The blast radius of misuse is minimal—an agent could only access metadata about project structure, not patient data or sensitive information beyond what it already has access to.
From the tool's definition Tool description states 'Get the mapping' which is a retrieval operation with no modification. The verb 'Get' and the context of 'mapping' indicate a query/fetch operation that returns existing data structures without side effects.
Attacks that exploit this kind of access
Get the mapping of instruments to events (longitudinal projects only). 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 get_instrument_event_mappings: 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.
get_instrument_event_mappings 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 get_instrument_event_mappings 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 get_instrument_event_mappings. 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.
get_instrument_event_mappings 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 →