AI agents call steer_logs to retrieve information from Git Steer 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 audit log entries without creating, modifying, deleting, or executing any actions. It is purely informational/read-only in nature, presenting historical data about system activities. The low severity reflects minimal blast radius—an AI agent misusing this tool could only inappropriately access logs but cannot alter system state or trigger operations.
From the tool's definition Tool name 'steer_logs' and description 'Show recent audit log entries' indicate retrieval of existing log data with no modification or execution capability.
Attacks that exploit this kind of access
Show recent audit log entries. It is categorised as a Read tool in the Git Steer MCP Server, which means it retrieves data without modifying state.
Register the Git Steer MCP server in PolicyLayer and add a rule for steer_logs: 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 Git Steer. Nothing to install.
steer_logs 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 steer_logs 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 steer_logs. 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.
steer_logs is provided by the Git Steer MCP server (ry-ops/git-steer). 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 →