bp_update_reading
AI agents use bp_update_reading to create or update resources in Blood Pressure Tool — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Blood Pressure Tool environment.
This tool modifies existing blood pressure data. While the description is empty, the name and server context clearly indicate it updates (modifies) readings reversibly. This is a Write operation—modifications can be corrected or reverted by subsequent updates. It is not Destructive (delete is separate), not Execute (doesn't run arbitrary code), and not Read (actively changes data).
From the tool's definition Tool name is 'bp_update_reading' and sibling tools include 'bp_create_reading', 'bp_delete_reading', 'bp_read_readings', indicating a CRUD system.
Attacks that exploit this kind of access
bp_update_reading. It is categorised as a Write tool in the Blood Pressure Tool MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Blood Pressure Tool MCP server in PolicyLayer and add a rule for bp_update_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_update_reading is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the bp_update_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_update_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_update_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 →