AI agents invoke generate_load to trigger actions in Otel. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool executes a mimic profile repeatedly to generate load/traffic against OTLP endpoints. It triggers external operations whose effects depend on the arguments (profile type, duration, rate). It is not merely reading data, nor is it writing a single record — it actively drives sustained execution of traffic simulation. Misuse could flood telemetry endpoints or exhaust resources, warranting medium severity.
From the tool's definition 'Repeatedly run a mimic profile to simulate sustained traffic' — triggers repeated external operations (OTLP telemetry emissions) in a sustained loop
Attacks that exploit this kind of access
Repeatedly run a mimic profile to simulate sustained traffic. It is categorised as a Execute tool in the Otel MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Otel MCP server in PolicyLayer and add a rule for generate_load: 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 Otel. Nothing to install.
generate_load is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the generate_load 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 generate_load. 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.
generate_load is provided by the Otel MCP server (probsjustin/otel_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 →