sap_trade_journal_query
Free local tool. Queries the trade journal with filters. Returns matching entries with count and total P&L. No x402 charge. SAP MCP execution guidance: Intent: Solana value-action or trading workflow. Pricing: free; call directly without x402. Routing: free hosted call; call directly and keep it ...
This record as markdown: /tools/oobe-protocol-labs-sap-mcp-server/sap-trade-journal-query.md
What sap_trade_journal_query does on Sap
AI agents call sap_trade_journal_query to retrieve information from Sap without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
to | string | — | End date ISO 8601. |
from | string | — | Start date ISO 8601. |
type | string | — | Filter by type. |
limit | number | — | Max results. Default 100. |
market | string | — | Filter by market. |
status | string | — | Filter by status. |
Parameters from the server's own tool schema.
Why sap_trade_journal_query is rated Low
Tool retrieves and filters trade journal data without modifying state or executing transactions.
From the tool's definition Queries the trade journal with filters. Returns matching entries with count and total P&L.
Attacks that exploit this kind of access
The rule that runs sap_trade_journal_query safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Sap, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For sap_trade_journal_query, this is the rule to start with:
sap_trade_journal_query is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Sap, apply this rule, and every sap_trade_journal_query call is checked against it from then on.
Questions about sap_trade_journal_query
Free local tool. Queries the trade journal with filters. Returns matching entries with count and total P&L. No x402 charge. SAP MCP execution guidance: Intent: Solana value-action or trading workflow. Pricing: free; call directly without x402. Routing: free hosted call; call directly and keep it small/exact when possible. Signer boundary: hosted reads/builders never receive keypair bytes; value-moving results must be finalized locally when signing is required. It is categorised as a Read tool in the Sap MCP Server, which means it retrieves data without modifying state.
sap_trade_journal_query accepts 6 parameters: to, from, type, limit, market, status. The full parameter table on this page comes from the server's own tool schema.
Register the Sap MCP server in PolicyLayer and add a rule for sap_trade_journal_query: 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 Sap. Nothing to install.
sap_trade_journal_query 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 sap_trade_journal_query 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 sap_trade_journal_query. 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.
sap_trade_journal_query is provided by the Sap MCP server (https://mcp.sap.oobeprotocol.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Sap, and thousands of servers like it.
This server
Across the catalogue