bp_delete_reading
AI agents call bp_delete_reading to permanently remove resources in Blood Pressure Tool — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes blood pressure health records. Deletion of medical data cannot be undone and represents a destructive action. While the description is empty, the name combined with the server description clearly establishes destructive capability.
From the tool's definition Tool name 'bp_delete_reading' indicates deletion of blood pressure readings; server description explicitly lists 'delete' as a capability; deletion is irreversible.
Attacks that exploit this kind of access
bp_delete_reading. It is categorised as a Destructive tool in the Blood Pressure Tool MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Blood Pressure Tool MCP server in PolicyLayer and add a rule for bp_delete_reading: 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 Blood Pressure Tool. Nothing to install.
bp_delete_reading 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 bp_delete_reading 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 bp_delete_reading. 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.
bp_delete_reading is provided by the Blood Pressure Tool MCP server (mclarkson/bptool). 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 →