get_cross_chain_activity
AI agents call get_cross_chain_activity to retrieve information from Wormhole Metrics without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and analyzes blockchain metrics without modifying state or executing code. It queries data about cross-chain transaction activity. While it deals with financial protocols, it only reads aggregate metrics, not moves money or commits financial obligations. Severity is low because the blast radius of misuse is limited to information disclosure with no financial impact or external side effects.
From the tool's definition Tool name 'get_cross_chain_activity' with 'get_' prefix indicates data retrieval. Server description states it 'analyzes cross-chain activity' and 'provides insights into transaction volumes' and 'KPIs'.
Attacks that exploit this kind of access
get_cross_chain_activity. It is categorised as a Read tool in the Wormhole Metrics MCP Server, which means it retrieves data without modifying state.
Register the Wormhole Metrics MCP server in PolicyLayer and add a rule for get_cross_chain_activity: 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 Wormhole Metrics. Nothing to install.
get_cross_chain_activity 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_cross_chain_activity 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_cross_chain_activity. 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_cross_chain_activity is provided by the Wormhole Metrics MCP server (kukapay/wormhole-metrics-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 →