删除我的某只基金持仓记录
AI agents call remove_portfolio to permanently remove resources in Cn Funds — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
An AI agent that decides to call remove_portfolio doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Cn Funds is gone — there is no undo for destructive operations.
Attacks that exploit this kind of access
删除我的某只基金持仓记录. It is categorised as a Destructive tool in the Cn Funds MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Cn Funds MCP server in PolicyLayer and add a rule for remove_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 Cn Funds. Nothing to install.
remove_portfolio is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the remove_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 remove_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.
remove_portfolio is provided by the Cn Funds MCP server (smallke/cn-funds-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.