get_transactions_by_date_range

Get all transactions within a date range.

Server Investment Statement MCP Server vinnycarter05/investing-mcp
Category Read
Risk class Low
Parameters 00 required

What get_transactions_by_date_range does on Investment Statement MCP Server

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

Why get_transactions_by_date_range needs a policy

The tool retrieves historical transaction data filtered by date parameters. This is a query operation with no side effects—it does not create, modify, delete, or execute actions. While the tool accesses sensitive financial data (transaction history), its low blast radius (information disclosure only, no financial obligation or data loss) places it in the Read category with low severity.

From the tool's definition Tool name 'get_transactions_by_date_range' and description 'Get all transactions within a date range' indicate pure data retrieval with no modification or deletion.

Questions about get_transactions_by_date_range

What does the get_transactions_by_date_range tool do? +

Get all transactions within a date range. It is categorised as a Read tool in the Investment Statement MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_transactions_by_date_range? +

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

What risk level is get_transactions_by_date_range? +

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

Can I rate-limit get_transactions_by_date_range? +

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

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

get_transactions_by_date_range is provided by the Investment Statement MCP Server MCP server (vinnycarter05/investing-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.