New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

get_pre_upgrade_delivery_record

A read tool on the Bybit MCP server.

SERVERBybit SOURCEjohnnywic/bybit-mcp
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/johnnywic-bybit-mcp/get-pre-upgrade-delivery-record.md

What get_pre_upgrade_delivery_record does on Bybit

AI agents call get_pre_upgrade_delivery_record to retrieve information from Bybit without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_pre_upgrade_delivery_record is rated Low

This tool retrieves historical delivery records without creating, modifying, deleting, or executing any operations. It is a pure read operation that fetches data about past deliveries, making it a Read category tool with low severity since it only accesses data.

From the tool's definition Tool name 'get_pre_upgrade_delivery_record' uses the verb 'get', which retrieves historical delivery record data. The description states 'Get pre-upgrade delivery record', indicating a query/retrieval operation with no modification or side effects.

Questions about get_pre_upgrade_delivery_record

What does the get_pre_upgrade_delivery_record tool do? +

get_pre_upgrade_delivery_record is a read tool on the Bybit MCP server. It is categorised as a Read tool in the Bybit MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_pre_upgrade_delivery_record? +

Register the Bybit MCP server in PolicyLayer and add a rule for get_pre_upgrade_delivery_record: 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 Bybit. Nothing to install.

What risk level is get_pre_upgrade_delivery_record? +

get_pre_upgrade_delivery_record is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_pre_upgrade_delivery_record? +

Yes. Add a rate_limit block to the get_pre_upgrade_delivery_record 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.

How do I block get_pre_upgrade_delivery_record completely? +

Set action: deny in the PolicyLayer policy for get_pre_upgrade_delivery_record. 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.

What MCP server provides get_pre_upgrade_delivery_record? +

get_pre_upgrade_delivery_record is provided by the Bybit MCP server (johnnywic/bybit-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Bybit, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Bybit's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.