Get current energy and bandwidth prices from all Merx providers, sorted by best (minimum) price across all duration tiers. Each provider lists ALL its duration tiers (5min/1h/1d/7d/30d etc) — short rentals are usually more expensive per unit than long ones, so always check tier-by-tier. Optionall...
AI agents call get_prices to retrieve information from MERX - TRON Resource Exchange without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves pricing data from multiple providers without side effects. It is a straightforward query operation that reads current market prices and returns them sorted and optionally filtered. There are no capabilities to modify data, execute code, delete records, or move funds. The low severity reflects minimal risk even if misused—an agent could only retrieve information about prices.
From the tool's definition Tool description states 'Get current energy and bandwidth prices' and 'No auth required.' The verb 'Get' indicates retrieval only. No modification, execution, deletion, or financial transaction occurs.
Attacks that exploit this kind of access
Get current energy and bandwidth prices from all Merx providers, sorted by best (minimum) price across all duration tiers. Each provider lists ALL its duration tiers (5min/1h/1d/7d/30d etc) — short rentals are usually more expensive per unit than long ones, so always check tier-by-tier. Optionally filter by exact duration in seconds. No auth required. It is categorised as a Read tool in the MERX - TRON Resource Exchange MCP Server, which means it retrieves data without modifying state.
Register the MERX - TRON Resource Exchange MCP server in PolicyLayer and add a rule for get_prices: 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 MERX - TRON Resource Exchange. Nothing to install.
get_prices 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_prices 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_prices. 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_prices is provided by the MERX - TRON Resource Exchange MCP server (Hovsteder/merx-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 →