remove_field
AI agents call remove_field to permanently remove resources in Redcap — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Although description is uninformative, the tool name 'remove_field' combined with the REDCap context (where fields are permanent schema components) indicates irreversible deletion. This is more severe than Write (which is reversible) and aligns with the Destructive category pattern evident in sibling tools. High confidence due to clear naming convention and domain context, despite missing description.
From the tool's definition Tool name is 'remove_field' which indicates deletion/removal of data structure. Server context shows management of research data in REDCap (a clinical data management system).
Attacks that exploit this kind of access
remove_field. It is categorised as a Destructive tool in the Redcap MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Redcap MCP server in PolicyLayer and add a rule for remove_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.
remove_field is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the remove_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.
Set action: deny in the PolicyLayer policy for remove_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.
remove_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.
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 →