revision
The revision (commit hash, branch name, tag) to show (string, required)
This record as markdown: /tools/io-github-aifity-omnigit-mcp/revision.md
What revision does on GitHub
AI agents call revision to retrieve information from GitHub without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why revision is rated Low
This tool appears to be a parameter for retrieving or showing data about a specific git revision. It has no side effects—it simply specifies which commit, branch, or tag to query. This is consistent with Read category tools that retrieve data without modification.
From the tool's definition The tool accepts a revision identifier (commit hash, branch name, or tag) as a parameter. This is a lookup/query parameter used to specify which git revision to display or retrieve information about.
Attacks that exploit this kind of access
The rule that runs revision safely
PolicyLayer is an MCP gateway: it sits between your AI agents and GitHub, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For revision, this is the rule to start with:
revision is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect GitHub, apply this rule, and every revision call is checked against it from then on.
Questions about revision
The revision (commit hash, branch name, tag) to show (string, required). It is categorised as a Read tool in the GitHub MCP Server, which means it retrieves data without modifying state.
Register the GitHub MCP server in PolicyLayer and add a rule for revision: 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 GitHub. Nothing to install.
revision 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 revision 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 revision. 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.
revision is provided by the GitHub MCP server (oci:ghcr.io/aifity/omnigit-mcp:0.5.0). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on GitHub, and thousands of servers like it.
This server
Across the catalogue