get_split_history

Get stock split history for a company including forward and reverse splits with dates, ratios,

Server Signal8 MCP Server signal8ai/signal8-mcp
Category Read
Risk class Low
Parameters 00 required

What get_split_history does on Signal8 MCP Server

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

Why get_split_history needs a policy

This tool queries and retrieves historical stock split information—a factual, immutable dataset. It performs no data creation, modification, deletion, or execution of code/commands. The caller cannot influence outcomes or cause side effects through parameters. This is a straightforward Read operation with minimal risk if misused by an AI agent, as it only accesses existing public financial reference data.

From the tool's definition Tool name is 'get_split_history' and description indicates it retrieves historical stock split data ('Get stock split history for a company including forward and reverse splits with dates, ratios').

Questions about get_split_history

What does the get_split_history tool do? +

Get stock split history for a company including forward and reverse splits with dates, ratios,. It is categorised as a Read tool in the Signal8 MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_split_history? +

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

What risk level is get_split_history? +

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

Can I rate-limit get_split_history? +

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

Set action: deny in the PolicyLayer policy for get_split_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_split_history? +

get_split_history is provided by the Signal8 MCP Server MCP server (signal8ai/signal8-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.