Low Risk

get_code_owners

Git-based code ownership: who contributed most to specific files (git shortlog). Requires git. Use to identify who to ask about specific files. For symbol-level ownership use get_symbol_owners instead. Read-only. Returns JSON: [{ file, owners: [{ author, commits, percentage }] }].

How to control get_code_owners ↓

AI agents call get_code_owners 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 tool queries git history to retrieve code ownership information based on commit statistics. It has no side effects, cannot modify or delete data, and does not execute code or perform financial operations. It is purely informational retrieval, making it a Read category tool with low severity.

From the tool's definition Tool description explicitly states 'Read-only' and 'git shortlog' which queries git history. Returns ownership metadata without modifying anything. Uses: 'get code owners', 'who contributed most', 'identify who to ask' — all retrieval operations.

Documented attack patterns abuse exactly the kind of access get_code_owners 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_code_owners:

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

get_code_owners 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_code_owners tool do? +

Git-based code ownership: who contributed most to specific files (git shortlog). Requires git. Use to identify who to ask about specific files. For symbol-level ownership use get_symbol_owners instead. Read-only. Returns JSON: [{ file, owners: [{ author, commits, percentage }] }]. 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_code_owners? +

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

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

Can I rate-limit get_code_owners? +

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

Set action: deny in the PolicyLayer policy for get_code_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_code_owners? +

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

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.