AI agents use add_verified_example to create or update resources in Tron — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Tron environment.
This tool modifies a knowledge base by inserting new code examples. It is a Write operation because it creates new data reversibly—examples can be removed or modified later. Severity is medium because misuse could pollute the knowledge base with incorrect or malicious code examples that other users might reference, but the impact is limited to informational content rather than direct financial or system harm.
From the tool's definition Tool name includes 'add' and description states 'Add a new verified code example to the knowledge base', indicating it creates and stores new data persistently.
Attacks that exploit this kind of access
Add a new verified code example to the knowledge base. It is categorised as a Write tool in the Tron MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Tron MCP server in PolicyLayer and add a rule for add_verified_example: 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.
add_verified_example is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the add_verified_example 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 add_verified_example. 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.
add_verified_example 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 →