Stores a note in the current MCP session.
AI agents use add_note to create or update resources in Example Mcp Server Streamable Http — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Example Mcp Server Streamable Http environment.
This tool creates or modifies data (adding a note) in a reversible manner. It does not delete, execute code, or cause destructive effects. The scope is limited to the current session, making severity low. High confidence due to clear descriptive language indicating a write operation.
From the tool's definition Tool description states 'Stores a note in the current MCP session' — a create/write operation that adds data to session storage.
Attacks that exploit this kind of access
Stores a note in the current MCP session. It is categorised as a Write tool in the Example Mcp Server Streamable Http MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Example Mcp Server Streamable Http MCP server in PolicyLayer and add a rule for add_note: 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 Example Mcp Server Streamable Http. Nothing to install.
add_note 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 add_note 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 add_note. 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.
add_note is provided by the Example Mcp Server Streamable Http MCP server (yigitkonur/example-mcp-stateful). 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 →