get_stock_history

Return an ETF-stock share-count history.

SERVEREtfedge SOURCEa7351220/etfedge-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade A, identity unverified Pull the record →

This record as markdown: /tools/a7351220-etfedge-mcp/get-stock-history.md

WHAT IT DOES

What get_stock_history does on Etfedge

AI agents call get_stock_history to retrieve information from Etfedge without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why get_stock_history is rated Low

Tool retrieves historical share count data without modification or side effects.

From the tool's definition Return an ETF-stock share-count history

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_stock_history safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Etfedge, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_stock_history, this is the rule to start with:

get_stock_history Allowed

get_stock_history is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_stock_history": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Etfedge, apply this rule, and every get_stock_history call is checked against it from then on.

FAQ

Questions about get_stock_history

What does the get_stock_history tool do? +

Return an ETF-stock share-count history. It is categorised as a Read tool in the Etfedge MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_stock_history? +

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

What risk level is get_stock_history? +

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

Can I rate-limit get_stock_history? +

Yes. Add a rate_limit block to the get_stock_history 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_stock_history completely? +

Set action: deny in the PolicyLayer policy for get_stock_history. 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_stock_history? +

get_stock_history is provided by the Etfedge MCP server (a7351220/etfedge-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Etfedge, and thousands of servers like it.

This server

All 13 Etfedge tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_file_snippet on ACE-MCP →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →