Returns every token/coin delisting announcement from MEXC
AI agents call get_delistings to retrieve information from MEXC Announcements MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves historical delisting announcements from MEXC. It performs no write, execute, destructive, or financial operations. The information returned is already-published announcements. Even though delistings are significant exchange events, the tool itself only reads and returns data without triggering any action or modifying state.
From the tool's definition Tool description states it 'Returns every token/coin delisting announcement from MEXC' — a retrieval operation with no modification or side effects.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Returns every token/coin delisting announcement from MEXC. It is categorised as a Read tool in the MEXC Announcements MCP MCP Server, which means it retrieves data without modifying state.
Register the MEXC Announcements MCP server in PolicyLayer and add a rule for get_delistings: 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 MEXC Announcements MCP. Nothing to install.
get_delistings 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_delistings 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_delistings. 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_delistings is provided by the MEXC Announcements MCP server (kukapay/mexc-announcements-mcp). 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 →