orderBy
Order issues by field. If provided, the 'direction' also needs to be provided. (string, optional)
This record as markdown: /tools/io-github-aifity-omnigit-mcp/orderby.md
What orderBy does on GitHub
AI agents call orderBy 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 orderBy is rated Low
This is a query parameter or helper function that sorts retrieved issue data by specified fields. It retrieves or organizes data without creating, modifying, deleting, or executing operations. The 'optional' nature and directional parameter confirm it is a read-only sorting utility, typical of list/filter operations. No side effects, no data mutation, no external execution.
From the tool's definition Tool name 'orderBy' and description 'Order issues by field' indicate a sorting/filtering operation on existing data with no modification capability.
Attacks that exploit this kind of access
The rule that runs orderBy 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 orderBy, this is the rule to start with:
orderBy 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 orderBy call is checked against it from then on.
Questions about orderBy
Order issues by field. If provided, the 'direction' also needs to be provided. (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 orderBy: 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.
orderBy 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 orderBy 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 orderBy. 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.
orderBy 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