AI agents call config_show 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 performs a retrieval operation ('show/display') on configuration data. There is no indication of modification, deletion, execution, or financial impact. The verb 'show' and the absence of any action words like 'set', 'update', 'delete', or 'trigger' confirm this is a Read operation with low severity since it only exposes configuration details without enabling agent actions that could cause harm.
From the tool's definition Tool name 'config_show' and description 'Display current configuration' indicate a read-only operation that retrieves and presents configuration data without modification or side effects.
Attacks that exploit this kind of access
Display current configuration. 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 config_show: 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.
config_show 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 config_show 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 config_show. 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.
config_show 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 →