propose_tickers_tool
AI agents call propose_tickers_tool to retrieve information from PM-MCP (Portfolio Management MCP Server) without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name indicates it proposes or suggests tickers (stock symbols), which is a read-like operation that retrieves or queries investment data without modifying state. However, confidence is reduced due to empty description. If the tool actually executes trades or commits financial positions, classification should be elevated to Execute or Financial.
From the tool's definition Tool name 'propose_tickers_tool' suggests retrieval/suggestion of ticker symbols. No description provided to confirm functionality.
Attacks that exploit this kind of access
propose_tickers_tool. It is categorised as a Read tool in the PM-MCP (Portfolio Management MCP Server) MCP Server, which means it retrieves data without modifying state.
Register the PM-MCP (Portfolio Management MCP Server) MCP server in PolicyLayer and add a rule for propose_tickers_tool: 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.
propose_tickers_tool is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the propose_tickers_tool 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 propose_tickers_tool. 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.
propose_tickers_tool 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 →