get_endpoint_analytics

Per-route analytics: request count, error rate, latency, caller services. Requires OTLP trace ingestion. Read-only, queries external runtime data. Use to understand endpoint performance and traffic. Returns JSON: { uri, method, requestCount, errorRate, latency, callerServices }.

SERVERTrace SOURCEnikolai-vysotskyi/trace-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/nikolai-vysotskyi-trace-mcp/get-endpoint-analytics.md

WHAT IT DOES

What get_endpoint_analytics does on Trace

AI agents call get_endpoint_analytics to retrieve information from Trace without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why get_endpoint_analytics is rated Low

This tool retrieves and queries telemetry data from an external observability system (OTLP trace ingestion). It has no side effects, performs no modifications, executions, or destructive operations. It solely reads pre-existing runtime analytics to provide performance insights.

From the tool's definition Tool description states: 'Read-only, queries external runtime data' and 'Per-route analytics: request count, error rate, latency, caller services' with return fields limited to observability metrics (uri, method, requestCount, errorRate, latency,…

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_endpoint_analytics safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Trace, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_endpoint_analytics, this is the rule to start with:

get_endpoint_analytics Allowed

get_endpoint_analytics is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_endpoint_analytics": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Trace, apply this rule, and every get_endpoint_analytics call is checked against it from then on.

FAQ

Questions about get_endpoint_analytics

What does the get_endpoint_analytics tool do? +

How do I enforce a policy on get_endpoint_analytics? +

Register the Trace MCP server in PolicyLayer and add a rule for get_endpoint_analytics: 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 Trace. Nothing to install.

What risk level is get_endpoint_analytics? +

get_endpoint_analytics is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_endpoint_analytics? +

Yes. Add a rate_limit block to the get_endpoint_analytics 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.

How do I block get_endpoint_analytics completely? +

Set action: deny in the PolicyLayer policy for get_endpoint_analytics. 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.

What MCP server provides get_endpoint_analytics? +

get_endpoint_analytics is provided by the Trace MCP server (nikolai-vysotskyi/trace-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Trace, and thousands of servers like it.

This server

All 191 Trace tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_file_snippet on ACE-MCP →get_torrent_detail on M-Team MCP Server →get_customer_data on 08-AI-Business-Agent → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →