View Git commit history for the Ansible project — shows configuration change history, backup timestamps, and diffs.
AI agents call ansible_git_log to retrieve information from Multi-Tool 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 and displays historical information from Git logs without modifying, deleting, or executing any operations. It is a read-only query operation with minimal blast radius if accessed by an AI agent without authorization, as it only exposes version control metadata and historical diffs.
From the tool's definition Tool description states 'View Git commit history' and 'shows configuration change history, backup timestamps, and diffs' — purely retrieval operations with no modifications or side effects.
Attacks that exploit this kind of access
View Git commit history for the Ansible project — shows configuration change history, backup timestamps, and diffs. It is categorised as a Read tool in the Multi-Tool MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Multi-Tool MCP Server MCP server in PolicyLayer and add a rule for ansible_git_log: 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 Multi-Tool MCP Server. Nothing to install.
ansible_git_log 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 ansible_git_log 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 ansible_git_log. 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.
ansible_git_log is provided by the Multi-Tool MCP Server MCP server (shawn-falconbury/mcp-server). 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 →