Reads content of a file from an Azure DevOps Git repository.
AI agents call git.file to retrieve information from Azure DevOps MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves file content from a repository without side effects. It is a pure read operation that queries existing data. The severity is low because reading file content from a repository has minimal blast radius—it accesses data that may already be accessible through other means, and cannot modify, delete, or cause irreversible changes. High confidence due to explicit 'Reads' language in the description.
From the tool's definition Tool name and description explicitly state it 'Reads content of a file from an Azure DevOps Git repository' with no modification, creation, or deletion of data.
Attacks that exploit this kind of access
Reads content of a file from an Azure DevOps Git repository. It is categorised as a Read tool in the Azure DevOps MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Azure DevOps MCP Server MCP server in PolicyLayer and add a rule for git.file: 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 Azure DevOps MCP Server. Nothing to install.
git.file 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 git.file 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 git.file. 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.
git.file is provided by the Azure DevOps MCP Server MCP server (varnierg/mcp-for-azure-devops). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the 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 →