Get OpenTelemetry repository issues
AI agents call list_opentelemetry_issues to retrieve information from Otel Instrumentation without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves issue information without modifying data or triggering external operations. It is a straightforward read operation with no side effects, making it a Read category tool with low severity.
From the tool's definition Tool name 'list_opentelemetry_issues' and description 'Get OpenTelemetry repository issues' indicate read-only retrieval of issue data from repositories.
Documented attack patterns abuse exactly the kind of access list_opentelemetry_issues gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Otel Instrumentation, and nothing reaches the server without passing your rules. This is the rule we recommend for list_opentelemetry_issues:
{
"version": "1",
"default": "deny",
"tools": {
"list_opentelemetry_issues": {}
}
}list_opentelemetry_issues is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get OpenTelemetry repository issues. It is categorised as a Read tool in the Otel Instrumentation MCP Server, which means it retrieves data without modifying state.
Register the Otel Instrumentation MCP server in PolicyLayer and add a rule for list_opentelemetry_issues: 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 Instrumentation. Nothing to install.
list_opentelemetry_issues 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 list_opentelemetry_issues 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 list_opentelemetry_issues. 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.
list_opentelemetry_issues is provided by the Otel Instrumentation MCP server (liatrio-labs/otel-instrumentation-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Otel Instrumentation, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
9 Otel Instrumentation tools catalogued and risk-classified — across an index of 43,000+ MCP servers.