List all schedules with optional filtering
AI agents call list_schedules 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/queries existing schedule data with optional filtering parameters. It has no capability to create, modify, delete, or execute operations. The 'list' verb and 'filtering' parameters are characteristic of Read operations. Within the context of a payment processing server, listing schedules presents minimal risk as it only exposes data retrieval functionality.
From the tool's definition Tool name 'list_schedules' and description 'List all schedules with optional filtering' indicates a query operation that retrieves schedule data without modification or execution of side effects.
Attacks that exploit this kind of access
List all schedules with optional filtering. 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_schedules: 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_schedules 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_schedules 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_schedules. 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_schedules 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 →