get_redemption_orders
Get redemption orders, optionally filtered by timestamp or price range
This record as markdown: /tools/indigoprotocol-indigo-mcp/get-redemption-orders.md
What get_redemption_orders does on Indigo Protocol MCP
AI agents call get_redemption_orders to retrieve information from Indigo Protocol MCP 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 |
|---|---|---|---|
in_range | boolean | — | Filter by price range |
timestamp | number | — | Unix timestamp in milliseconds |
Parameters from the server's own tool schema.
Why get_redemption_orders is rated Low
This tool retrieves and queries existing redemption order data with optional filtering parameters. It performs no mutations, deletions, or external state changes. The filtering by timestamp or price range indicates a passive data retrieval function typical of Read category operations.
From the tool's definition Tool name 'get_redemption_orders' uses verb 'get'; description states 'Get redemption orders, optionally filtered' — a retrieval/query operation with no state modifications
Attacks that exploit this kind of access
The rule that runs get_redemption_orders safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Indigo Protocol MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_redemption_orders, this is the rule to start with:
get_redemption_orders 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 Indigo Protocol MCP, apply this rule, and every get_redemption_orders call is checked against it from then on.
Questions about get_redemption_orders
Get redemption orders, optionally filtered by timestamp or price range. It is categorised as a Read tool in the Indigo Protocol MCP MCP Server, which means it retrieves data without modifying state.
get_redemption_orders accepts 2 parameters: in_range, timestamp. The full parameter table on this page comes from the server's own tool schema.
Register the Indigo Protocol MCP server in PolicyLayer and add a rule for get_redemption_orders: 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 Indigo Protocol MCP. Nothing to install.
get_redemption_orders 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 get_redemption_orders 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 get_redemption_orders. 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.
get_redemption_orders is provided by the Indigo Protocol MCP server (indigoprotocol/indigo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Indigo Protocol, and thousands of servers like it.
This server
Across the catalogue