AI agents call get_historical to retrieve information from Sahmk without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Despite the empty description, the tool name and context strongly suggest this retrieves historical market or financial data (e.g., historical prices, trends). This is a read-only operation with no side effects.
From the tool's definition Tool name 'get_historical' and sibling tools (get_quote, get_quotes, get_financials, get_ratios, get_market_summary) all indicate data retrieval operations.
Documented attack patterns abuse exactly the kind of access get_historical gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Sahmk, and nothing reaches the server without passing your rules. This is the rule we recommend for get_historical:
{
"version": "1",
"default": "deny",
"tools": {
"get_historical": {}
}
}get_historical is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
get_historical. It is categorised as a Read tool in the Sahmk MCP Server, which means it retrieves data without modifying state.
Register the Sahmk MCP server in PolicyLayer and add a rule for get_historical: 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 Sahmk. Nothing to install.
get_historical 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 get_historical 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 get_historical. 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.
get_historical is provided by the Sahmk MCP server (sahmk-sa/sahmk-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Sahmk, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
12 Sahmk tools catalogued and risk-classified — across an index of 43,000+ MCP servers.