since

Only show notifications updated after the given time (ISO 8601 format) (string, 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/since.md

WHAT IT DOES

What since does on GitHub

AI agents call since 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 since is rated Low

This is a filter parameter for retrieving notifications based on a timestamp criterion. It retrieves or queries data (notifications) with no side effects—no creation, modification, deletion, code execution, or financial impact. The tool purely constrains what data is returned from an existing read operation.

From the tool's definition Tool name 'since' with description 'Only show notifications updated after the given time' indicates filtering/querying notifications without modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

since Allowed

since 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": {
    "since": {}
  }
}

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 since call is checked against it from then on.

FAQ

Questions about since

What does the since tool do? +

Only show notifications updated after the given time (ISO 8601 format) (string, 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 since? +

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

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

Can I rate-limit since? +

Yes. Add a rate_limit block to the since 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 since completely? +

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

since 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 →