score_tickers
AI agents call score_tickers to retrieve information from Portfolio Rotation 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 suggests a query/scoring operation rather than creation, modification, deletion, or execution. Within the portfolio rotation analysis context, scoring ticker symbols would be a read operation that retrieves or computes analytical metrics without side effects. The low severity reflects that such scoring operations have no blast radius on financial positions or external systems.
From the tool's definition Tool name 'score_tickers' indicates retrieval and evaluation of ticker scores across 5 dimensions. The server context describes 'score holdings and candidates', suggesting analytical scoring without modification of data or execution of external operations.
Attacks that exploit this kind of access
score_tickers. It is categorised as a Read tool in the Portfolio Rotation MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Portfolio Rotation MCP Server MCP server in PolicyLayer and add a rule for score_tickers: 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 Portfolio Rotation MCP Server. Nothing to install.
score_tickers 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 score_tickers 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 score_tickers. 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.
score_tickers is provided by the Portfolio Rotation MCP Server MCP server (mothanaprime/rebalance-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 →