Low Risk

get_symbol_complexity_trend

Single symbol complexity over git history: cyclomatic, nesting, params, lines at past commits. Requires git. Use to track a specific function

How to control get_symbol_complexity_trend ↓

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

Low Risk

This is a read-only analysis tool that queries git history and computes static complexity metrics on existing code. It has no side effects—it does not execute code, modify source files, delete data, or trigger external operations. The data retrieved is purely informational for code intelligence purposes.

From the tool's definition Tool retrieves historical complexity metrics ('cyclomatic, nesting, params, lines at past commits') from git history without modifying code or executing external operations. The verb 'track' here means observe/query, not execute.

Documented attack patterns abuse exactly the kind of access get_symbol_complexity_trend gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Trace, and nothing reaches the server without passing your rules. This is the rule we recommend for get_symbol_complexity_trend:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_symbol_complexity_trend": {}
  }
}

get_symbol_complexity_trend is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Trace — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the get_symbol_complexity_trend tool do? +

Single symbol complexity over git history: cyclomatic, nesting, params, lines at past commits. Requires git. Use to track a specific function. It is categorised as a Read tool in the Trace MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_symbol_complexity_trend? +

Register the Trace MCP server in PolicyLayer and add a rule for get_symbol_complexity_trend: 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_symbol_complexity_trend? +

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

Can I rate-limit get_symbol_complexity_trend? +

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

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

get_symbol_complexity_trend 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.

Enforce policy on every Trace tool call.

Deterministic rules across all 178 Trace tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

178 Trace tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.