get_instrumentation_score_rules
AI agents call get_instrumentation_score_rules 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.
The 'get_' prefix and parallel to other read-only sibling tools (list_, get_) strongly suggest this retrieves instrumentation scoring rules without modification. The empty description lowers confidence slightly, but the tool's name and server context are consistent with data retrieval. No evidence of side effects, code execution, or data modification.
From the tool's definition Tool name 'get_instrumentation_score_rules' indicates retrieval of rules/specifications. Sibling tools on the same server (get_instrumentation_score_spec, get_opentelemetry_docs_by_language, list_opentelemetry_issues, list_opentelemetry_repos,…
Documented attack patterns abuse exactly the kind of access get_instrumentation_score_rules 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 get_instrumentation_score_rules:
{
"version": "1",
"default": "deny",
"tools": {
"get_instrumentation_score_rules": {}
}
}get_instrumentation_score_rules 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_instrumentation_score_rules. 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 get_instrumentation_score_rules: 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.
get_instrumentation_score_rules 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_instrumentation_score_rules 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_instrumentation_score_rules. 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_instrumentation_score_rules 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.