Add a comment to an alert
AI agents use add_alert_comment to create or update resources in My Portfolio MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your My Portfolio MCP Server environment.
This tool creates or modifies data (adding a comment) in a reversible manner. It does not execute code, delete data, move money, or trigger external operations. The blast radius is minimal—a misused comment adds benign metadata to an alert and can be easily removed or edited. This is straightforward Write category behavior.
From the tool's definition Tool name 'add_alert_comment' and description 'Add a comment to an alert' indicate creation of new comment data associated with an existing alert.
Attacks that exploit this kind of access
Add a comment to an alert. It is categorised as a Write tool in the My Portfolio MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the My Portfolio MCP Server MCP server in PolicyLayer and add a rule for add_alert_comment: 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 My Portfolio MCP Server. Nothing to install.
add_alert_comment 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_alert_comment 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_alert_comment. 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_alert_comment is provided by the My Portfolio MCP Server MCP server (udaybhasker-ub/my-portfolio-mcp). 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 →