List all occurrences (execution history) for a schedule
AI agents call list_schedule_occurrences to retrieve information from Omise MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries execution history for a recurring payment schedule, which is a non-destructive, read-only operation. It has no side effects on data or financial transactions—it only returns information about past schedule executions. While the server handles financial operations, this specific tool is purely informational.
From the tool's definition Tool name 'list_schedule_occurrences' and description 'List all occurrences (execution history) for a schedule' indicate a retrieval operation. The verb 'list' is explicitly a Read operation that queries historical data without modification.
Attacks that exploit this kind of access
List all occurrences (execution history) for a schedule. It is categorised as a Read tool in the Omise MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Omise MCP Server MCP server in PolicyLayer and add a rule for list_schedule_occurrences: 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 Omise MCP Server. Nothing to install.
list_schedule_occurrences 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 list_schedule_occurrences 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 list_schedule_occurrences. 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.
list_schedule_occurrences is provided by the Omise MCP Server MCP server (jun-omise/omise-mcp-alpha). 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 →