AI agents call get_documentation_status 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 status information about documentation and caching systems. It has no side effects, does not modify blockchain state, does not execute code or contracts, and does not involve financial transactions. It is purely informational and falls squarely within the Read category with low severity due to its benign nature.
From the tool's definition Tool name and description indicate it 'Get current status of documentation cache and examples' — a retrieval operation that queries metadata about cached documentation and examples without modifying state or executing transactions.
Attacks that exploit this kind of access
Get current status of documentation cache and 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_documentation_status: 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_documentation_status 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_documentation_status 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_documentation_status. 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_documentation_status 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 →