get_traces

SERVERTideways MCP Server SOURCE5hahil/tideways-mcp-server

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade A, identity unverified Pull the record →

This record as markdown: /tools/5hahil-tideways-mcp-server/get-traces.md

WHAT IT DOES

What get_traces does on Tideways MCP Server

AI agents call get_traces to retrieve information from Tideways MCP Server 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_traces is rated Low

This tool retrieves and examines pre-recorded trace data from a performance monitoring system. There is no indication that it modifies, deletes, or executes arbitrary code. It is a read-only query operation on historical performance data.

From the tool's definition Tool description states 'Analyze individual trace samples in JSON format' and 'Use for investigating specific slow requests' — these are query and analysis operations with no modification, creation, or deletion of data.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_traces safely

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

get_traces Allowed

get_traces 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_traces": {}
  }
}

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

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

FAQ

Questions about get_traces

What does the get_traces tool do? +

Analyze individual trace samples in JSON format for detailed bottleneck identification and performance debugging. Use for investigating specific slow requests, not system-wide statistics (use get_performance_metrics for aggregate data). It is categorised as a Read tool in the Tideways MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_traces? +

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

What risk level is get_traces? +

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

Can I rate-limit get_traces? +

Yes. Add a rate_limit block to the get_traces 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_traces completely? +

Set action: deny in the PolicyLayer policy for get_traces. 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_traces? +

get_traces is provided by the Tideways MCP Server MCP server (5hahil/tideways-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Tideways MCP Server, and thousands of servers like it.

This server

All 5 Tideways MCP Server 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 →aiva_get_affiliate on AIVA MCP Server → The MCP Attack Database →

Guides

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