update_portfolio
AI agents use update_portfolio to create or update resources in Sablier MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Sablier MCP Server environment.
This tool creates or modifies portfolio data (Write category) rather than executing transactions (Financial), deleting records (Destructive), or merely reading data (Read). Medium severity reflects that portfolio modifications could cause analytical errors or misleading insights, but the lack of details about whether it commits actual financial obligations prevents a higher classification.
From the tool's definition Tool name 'update_portfolio' with empty description indicates it modifies portfolio data. The server context mentions 'analyze portfolios' and financial instruments, confirming this operates on financial data structures.
Attacks that exploit this kind of access
update_portfolio. It is categorised as a Write tool in the Sablier MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Sablier MCP Server MCP server in PolicyLayer and add a rule for update_portfolio: 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 Sablier MCP Server. Nothing to install.
update_portfolio 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 update_portfolio 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 update_portfolio. 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.
update_portfolio is provided by the Sablier MCP Server MCP server (sablier-ai/sablier-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 →