get_commits_by_path

Get commits for a specific directory path from Bitbucket. Filters commits by time (default: last 7 days). Useful for analyzing recent changes in a module or package.

Server Error Tracker MCP Server wyccome/mcp-error-tracing
Category Read
Risk class Low
Parameters 00 required

What get_commits_by_path does on Error Tracker MCP Server

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

Why get_commits_by_path needs a policy

This is a query/fetch operation that retrieves historical commit data for analysis purposes. It does not modify, create, delete, or execute anything—it simply reads and returns commit information. The time-based filtering is a read-only parameter.

From the tool's definition Tool retrieves commits by path from Bitbucket with filtering capability (last 7 days default). Verbs 'Get' and 'retrieves' indicate data query operation with no modification, deletion, or code execution. No side effects mentioned.

Questions about get_commits_by_path

What does the get_commits_by_path tool do? +

Get commits for a specific directory path from Bitbucket. Filters commits by time (default: last 7 days). Useful for analyzing recent changes in a module or package. It is categorised as a Read tool in the Error Tracker MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_commits_by_path? +

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

What risk level is get_commits_by_path? +

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

Can I rate-limit get_commits_by_path? +

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

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

get_commits_by_path is provided by the Error Tracker MCP Server MCP server (wyccome/mcp-error-tracing). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.