megaeth_unsubscribe
AI agents invoke megaeth_unsubscribe to trigger actions in Chain Debugger MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Based on the naming pattern and the presence of a sibling 'megaeth_subscribe' tool, this tool likely cancels or removes an active blockchain event subscription. Canceling a subscription is an external operation with side effects (stopping data flow), placing it in Execute. The description is empty, so confidence is reduced.
From the tool's definition Tool name 'megaeth_unsubscribe' and empty description; sibling tool 'megaeth_subscribe' exists, implying this cancels an active subscription or event stream.
Attacks that exploit this kind of access
megaeth_unsubscribe. It is categorised as a Execute tool in the Chain Debugger MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Chain Debugger MCP Server MCP server in PolicyLayer and add a rule for megaeth_unsubscribe: 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 Chain Debugger MCP Server. Nothing to install.
megaeth_unsubscribe is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the megaeth_unsubscribe 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 megaeth_unsubscribe. 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.
megaeth_unsubscribe is provided by the Chain Debugger MCP Server MCP server (optimusopus/chain-debugger-mcp-server). 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 →