include_diff

Whether to include file diffs and stats in the response. Default is true. (boolean, optional)

SERVERGitHub SOURCEoci:ghcr.io/aifity/omnigit-mcp:0.5.0

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-aifity-omnigit-mcp/include-diff.md

WHAT IT DOES

What include_diff does on GitHub

AI agents call include_diff 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.

RISK

Why include_diff is rated Low

This is a query/presentation parameter for an API response. It determines what data is returned (diffs and stats) but performs no side effects, modifications, or operations on GitHub resources. It is purely read-oriented data retrieval with conditional output formatting.

From the tool's definition The tool is a boolean parameter that controls whether to 'include file diffs and stats in the response.' It retrieves or presents data differently based on the flag but does not modify, execute, delete, or create any resources.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs include_diff 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 include_diff, this is the rule to start with:

include_diff Allowed

include_diff is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "include_diff": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect GitHub, apply this rule, and every include_diff call is checked against it from then on.

FAQ

Questions about include_diff

What does the include_diff tool do? +

Whether to include file diffs and stats in the response. Default is true. (boolean, optional). It is categorised as a Read tool in the GitHub MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on include_diff? +

Register the GitHub MCP server in PolicyLayer and add a rule for include_diff: 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.

What risk level is include_diff? +

include_diff is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit include_diff? +

Yes. Add a rate_limit block to the include_diff 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.

How do I block include_diff completely? +

Set action: deny in the PolicyLayer policy for include_diff. 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.

What MCP server provides include_diff? +

include_diff 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.

KEEP EXPLORING

More on GitHub, and thousands of servers like it.

This server

All 245 GitHub tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →