AI agents call name 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.
Given the trace-mcp server's purpose of providing code navigation and analysis, a 'name' tool would typically query or retrieve names of code elements (functions, classes, modules, etc.) with no side effects. This is a Read operation. Low severity because it only accesses metadata. Confidence is reduced due to uninformative placeholder descriptions.
From the tool's definition Tool name 'name' and description 'description' are placeholders without substantive detail. Based on the server context (code intelligence, dependency graph analysis), a tool called 'name' most likely retrieves or returns naming/metadata information about…
Documented attack patterns abuse exactly the kind of access name 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 name:
{
"version": "1",
"default": "deny",
"tools": {
"name": {}
}
}name 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.
description. It is categorised as a Read tool in the Trace MCP Server, which means it retrieves data without modifying state.
Register the Trace MCP server in PolicyLayer and add a rule for name: 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.
name 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 name 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 name. 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.
name 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.
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.