Low Risk

get_relative_volume_stocks

相対出来高異常銘柄の検出

How to control get_relative_volume_stocks ↓

AI agents call get_relative_volume_stocks to retrieve information from Finviz MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

The tool detects stocks with relative volume anomalies—a passive screening operation that retrieves and queries stock data. It has no side effects, does not modify data, execute commands, delete records, or move money. It fits the 'Read' category as it simply fetches and analyzes existing market data to identify stocks meeting specific technical criteria.

From the tool's definition Tool name 'get_relative_volume_stocks' and description indicating detection of relative volume anomalies (relative volume surge/abnormality detection). This is a stock screening/detection function that retrieves and queries data from Finviz.

Documented attack patterns abuse exactly the kind of access get_relative_volume_stocks gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Finviz MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_relative_volume_stocks:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_relative_volume_stocks": {}
  }
}

get_relative_volume_stocks is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Finviz MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the get_relative_volume_stocks tool do? +

相対出来高異常銘柄の検出. It is categorised as a Read tool in the Finviz MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_relative_volume_stocks? +

Register the Finviz MCP Server MCP server in PolicyLayer and add a rule for get_relative_volume_stocks: 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 Finviz MCP Server. Nothing to install.

What risk level is get_relative_volume_stocks? +

get_relative_volume_stocks is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_relative_volume_stocks? +

Yes. Add a rate_limit block to the get_relative_volume_stocks 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.

How do I block get_relative_volume_stocks completely? +

Set action: deny in the PolicyLayer policy for get_relative_volume_stocks. 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.

What MCP server provides get_relative_volume_stocks? +

get_relative_volume_stocks is provided by the Finviz MCP Server MCP server (tradermonty/finviz-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Finviz MCP Server tool call.

Deterministic rules across all 35 Finviz MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

35 Finviz MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.