AI agents call get_chain_parameters to retrieve information from Tron without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves chain parameters (likely consensus rules, fee structures, block parameters, etc.) without modifying state, executing code, or producing financial effects. It is informational and read-only. Low severity because the data retrieved is public blockchain metadata with no sensitive account or transaction information, and no capability to alter system state.
From the tool's definition Tool name is 'get_chain_parameters' and description states 'Get current chain parameters' — a retrieval operation with no side effects. Consistent with Read category tools like 'get' and 'fetch' that query blockchain state.
Attacks that exploit this kind of access
Get current chain parameters. It is categorised as a Read tool in the Tron MCP Server, which means it retrieves data without modifying state.
Register the Tron MCP server in PolicyLayer and add a rule for get_chain_parameters: 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 Tron. Nothing to install.
get_chain_parameters 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_chain_parameters 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_chain_parameters. 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_chain_parameters is provided by the Tron MCP server (netts-official/tron_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 →