per_page
Results per page (max 50) (number, optional)
This record as markdown: /tools/io-github-aifity-omnigit-mcp/per-page.md
What per_page does on GitHub
AI agents call per_page 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 per_page is rated Low
This is a read-only utility parameter used to limit result set size in queries. It has no side effects, cannot modify or delete data, and cannot execute operations. It is a standard pagination control with minimal security risk.
From the tool's definition Tool is a pagination parameter ('Results per page') that controls query result size, with a maximum of 50 items. No data modification, deletion, or execution capability.
Attacks that exploit this kind of access
The rule that runs per_page 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 per_page, this is the rule to start with:
per_page 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 per_page call is checked against it from then on.
Questions about per_page
Results per page (max 50) (number, 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 per_page: 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.
per_page 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 per_page 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 per_page. 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.
per_page 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