AI agents call get_api_method_docs 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 reference documentation and examples from the TronGrid API—a purely informational operation with no side effects, state changes, financial impact, or code execution. It serves an informational purpose similar to accessing help files or API documentation. No blast radius exists from misuse since the tool only reads and returns documentation.
From the tool's definition Tool name 'get_api_method_docs' and description 'Get complete documentation for a TronGrid API method with verified examples' indicates retrieval and querying of documentation and reference information with no data modification or execution capability.
Attacks that exploit this kind of access
Get complete documentation for a TronGrid API method with verified examples. 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_api_method_docs: 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_api_method_docs 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_api_method_docs 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_api_method_docs. 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_api_method_docs 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 →