author
Author username or email address to filter commits by (string, optional)
This record as markdown: /tools/io-github-aifity-omnigit-mcp/author.md
What author does on GitHub
AI agents call author 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 author is rated Low
This is a read-only filter used to constrain commit queries by author. It has no side effects—it only narrows the scope of data retrieval. The low severity reflects minimal blast radius: an agent misusing this filter might retrieve unwanted commit history but cannot modify, delete, or execute code.
From the tool's definition Tool is a filter parameter for commits: 'Author username or email address to filter commits by'. It retrieves/queries commit data without modifying, deleting, or executing operations.
Attacks that exploit this kind of access
The rule that runs author 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 author, this is the rule to start with:
author 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 author call is checked against it from then on.
Questions about author
Author username or email address to filter commits by (string, optional). 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 author: 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.
author 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 author 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 author. 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.
author 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