Update a note
AI agents use note_update to create or update resources in MCP Object-Authz Lab — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Object-Authz Lab environment.
This tool modifies existing data (reversible write operation), placing it in the Write category. Severity is high rather than critical because the action is reversible and does not delete data or move money. However, in a deliberately vulnerable multi-tenant system, unauthorized note updates could expose confidentiality/integrity violations across tenants, elevating severity beyond 'medium'.
From the tool's definition Tool name 'note_update' and description 'Update a note' indicate modification of existing data. The server is explicitly described as 'vulnerable-by-design' for learning object-level authorization (BOLA/IDOR) bugs in multi-tenant environments, meaning this…
Attacks that exploit this kind of access
Update a note. It is categorised as a Write tool in the MCP Object-Authz Lab MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Object-Authz Lab MCP server in PolicyLayer and add a rule for note_update: 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 MCP Object-Authz Lab. Nothing to install.
note_update 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 note_update 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 note_update. 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.
note_update is provided by the MCP Object-Authz Lab MCP server (wrg-11/mcp-objauthz-lab). 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 →