Retrieve the latest trade volume and settlement status for an account.
AI agents call get_history to retrieve information from Northern Trust MCP Layer without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a data retrieval operation (get_history) that queries account trading history and settlement information. It has no side effects, does not execute trades, does not modify data, and does not move money. While the context is financial (Northern Trust, account data), the tool itself only reads/fetches existing data.
From the tool's definition Tool retrieves 'latest trade volume and settlement status' — purely informational queries with no modification, execution, or financial transaction capability.
Attacks that exploit this kind of access
Retrieve the latest trade volume and settlement status for an account. It is categorised as a Read tool in the Northern Trust MCP Layer MCP Server, which means it retrieves data without modifying state.
Register the Northern Trust MCP Layer MCP server in PolicyLayer and add a rule for get_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 Northern Trust MCP Layer. Nothing to install.
get_history 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_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.
Set action: deny in the PolicyLayer policy for get_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.
get_history is provided by the Northern Trust MCP Layer MCP server (vbzvibin/mcp_v3). 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 →