get_symbol_owners

Git blame-based symbol ownership: who wrote which lines of a specific symbol. Requires git. Use for fine-grained ownership of a specific function/class. For file-level ownership use get_code_owners instead. Read-only. Returns JSON: { symbol_id, owners: [{ author, lines, percentage }] }.

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-symbol-owners.md

WHAT IT DOES

What get_symbol_owners does on Trace

AI agents call get_symbol_owners 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_symbol_owners is rated Low

This tool retrieves and queries version control metadata (git blame) to determine code ownership. It has no side effects—it only reads and returns historical authorship data. The explicit 'Read-only' designation confirms it performs information retrieval without creating, modifying, deleting, or executing anything.

From the tool's definition Tool description explicitly states 'Read-only' and 'Git blame-based symbol ownership: who wrote which lines of a specific symbol'. Returns JSON data without modifying any code or configuration. Uses git blame to retrieve historical authorship information.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_symbol_owners 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_symbol_owners, this is the rule to start with:

get_symbol_owners Allowed

get_symbol_owners 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_symbol_owners": {}
  }
}

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_symbol_owners call is checked against it from then on.

FAQ

Questions about get_symbol_owners

What does the get_symbol_owners tool do? +

How do I enforce a policy on get_symbol_owners? +

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

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

Can I rate-limit get_symbol_owners? +

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

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

get_symbol_owners 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 →