Retrieve schedule information by ID
AI agents call retrieve_schedule 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 schedule information by its ID, which is a straightforward data lookup operation with no side effects. It does not create, modify, execute code, delete, or move money. The blast radius is minimal as it only reads payment schedule metadata that may already be accessible to authorized users.
From the tool's definition Tool name 'retrieve_schedule' and description 'Retrieve schedule information by ID' indicate a read-only query operation that fetches existing schedule data without modifying, executing, or deleting anything.
Attacks that exploit this kind of access
Retrieve schedule information by ID. 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 retrieve_schedule: 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.
retrieve_schedule 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 retrieve_schedule 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 retrieve_schedule. 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.
retrieve_schedule 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 →