Place a LIMIT order on Zebpay spot exchange with automatic currency conversion. Use this to buy or sell at a specific price. The order rests on the order book until it can be filled at the specified price or better. Important notes: - Supports BOTH quote currency (INR) and base currency (BTC) spe...
Part of the ZebPay MCP Server server.
Free to start. No card required.
AI agents call zebpay_spot_placeLimitOrder to retrieve information from ZebPay MCP Server without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though zebpay_spot_placeLimitOrder only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"zebpay_spot_placeLimitOrder": {}
}
}See the full ZebPay MCP Server policy for all 39 tools.
These attack patterns abuse exactly the kind of access zebpay_spot_placeLimitOrder gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Place a LIMIT order on Zebpay spot exchange with automatic currency conversion. Use this to buy or sell at a specific price. The order rests on the order book until it can be filled at the specified price or better. Important notes: - Supports BOTH quote currency (INR) and base currency (BTC) specifications - Automatic conversion using the provided limit price when needed - All quantities are trimmed to 6 decimal places - You must specify EITHER quoteOrderAmount OR amount (not both) How conversion works: For BUY orders: - User specifies quoteOrderAmount (100 INR) → Used directly as quoteOrderAmount - User specifies amount (0.0001 BTC) → Converted: 0.0001 × limit_price = INR value → Used as quoteOrderAmount For SELL orders: - User specifies amount (0.0005 BTC) → Used directly as amount - User specifies quoteOrderAmount (200 INR) → Converted: 200 ÷ limit_price = BTC quantity → Used as amount Example use cases: 1. User says. It is categorised as a Read tool in the ZebPay MCP Server MCP Server, which means it retrieves data without modifying state.
Register the ZebPay MCP Server MCP server in PolicyLayer and add a rule for zebpay_spot_placeLimitOrder: 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 ZebPay MCP Server. Nothing to install.
zebpay_spot_placeLimitOrder 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 zebpay_spot_placeLimitOrder 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 zebpay_spot_placeLimitOrder. 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.
zebpay_spot_placeLimitOrder is provided by the ZebPay MCP Server MCP server (ZebpayRajesh/zebpay-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 39 ZebPay MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.