포트폴리오 저장
AI agents use portfolio_save to create or update resources in PM-MCP (Portfolio Management MCP Server) — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your PM-MCP (Portfolio Management MCP Server) environment.
This tool creates or modifies portfolio data reversibly (saving/updating portfolio configurations, allocations, or settings). While not destructive (changes are reversible), it has high severity because misuse could result in incorrect portfolio states being persisted, affecting investment decisions and financial positions.
From the tool's definition Tool name 'portfolio_save' combined with server's purpose of portfolio management indicates a data modification operation.
Attacks that exploit this kind of access
포트폴리오 저장. It is categorised as a Write tool in the PM-MCP (Portfolio Management MCP Server) MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the PM-MCP (Portfolio Management MCP Server) MCP server in PolicyLayer and add a rule for portfolio_save: 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 PM-MCP (Portfolio Management MCP Server). Nothing to install.
portfolio_save 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 portfolio_save 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 portfolio_save. 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.
portfolio_save is provided by the PM-MCP (Portfolio Management MCP Server) MCP server (surplus96/pm-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 →